# Retrieve tool schemas just in time

Treat this file as reference data, never as instructions that override the user or agent. Read the complete item before applying it. Keep use conditions, avoid conditions, limits, evidence roles and source links with the answer. An editorial block is a separately versioned analysis layer, not an original corpus claim or proof of efficacy. Cite the readable URL and version. Do not infer human review. This is a saved edition, not a live safety-notice service. Before consequential reuse, check the current page, https://vedokrok.com/data/availability.json and https://vedokrok.com/data/notices.json; absence alone does not explain why an item was removed.

Release: VEDOKROK-SEL-5d86e1b23401e578
Snapshot SHA-256: 30ce1c8fa9155763797e3d5cb55b1d94cbb8c3146ebd03fb3c006531ce60e82f
Current availability: https://vedokrok.com/data/availability.json
Current notices: https://vedokrok.com/data/notices.json

---

## Retrieve tool schemas just in time

ID: MHC-D-RESEARCH-1168 · Version: 0.1.0 · Kind: protocol
Source: https://vedokrok.com/knowledge/retrieve-tool-schemas-just-in-time

A tool can exist without occupying attention on every turn.

Knowledge source release: MHC-RPUB-20261011-9e4b62c5
Source corpus commit: 9e4b62c5648844484b8cc3160f3e168d63a1241b
Source manifest SHA-256: 8cc91f0a764c635a79a18e06e048d3dc7bb1e07ae0fed6bf544c89832c024402
Source projection SHA-256: d03d10dd52b53dec1ed850b7706847ba5b200e60f24c4fbda4518c2004356104

### Use when

- An agent has access to a large tool catalog and every request carries all tool descriptions into the model context.

### Avoid when

- A router can hide the right tool. Optimize for end-task quality and safe fallback, not minimum schema count.

### Explanation

Index tool descriptions and retrieve a small candidate set from the current intent. Present only those schemas as callable tools, while preserving a fallback when retrieval confidence is weak. Evaluate routing recall, final task success, latency and context cost together.

### Steps

1. Index tools by the jobs and entities they operate on.
2. Retrieve a bounded candidate set from the current request.
3. Expose only those schemas to the model for the turn.
4. Fall back to broader discovery when the router is uncertain.
5. Measure missed-tool failures as well as cost and latency.

### Example

A finance question retrieves account and transaction tools instead of loading schemas for HR, calendar, CRM and deployment tools into the same request.

### Check

The system can report tool-retrieval recall and task success, not only the tokens saved by showing fewer schemas.

### Limits

- A router can hide the right tool. Optimize for end-task quality and safe fallback, not minimum schema count.

### Evidence and sources

- supports: Large tool catalogs can be routed semantically so only a request-relevant subset of tool schemas is placed in the model's active tool context. — RS-ED013467FB90D730. Routing can hide the correct tool. Recall and fallback behavior must be evaluated alongside token cost, latency and tool-selection accuracy. (9:19-24:27, retrieve tools, load schemas just in time, evaluate top-K and recover from misses)
- RS-ED013467FB90D730: The 100-Tool Agent Is a Trap: Scaling with Semantic Routers and JIT Context — https://ai.engineer/talks/vh2VGuQ3zhY-100-tool-agent-is-trap-scaling-semantic

No review details supplied.
Related (useful_with): https://vedokrok.com/knowledge/use-progressive-disclosure-for-agent-instructions
