The Problem
Without a registry, tool definitions get copy-pasted across prompts. Aget_weather tool might exist in 20 different prompts, each with slightly different parameter names, descriptions, or schemas. When you need to update it, you have to find and edit every copy. Some get missed, and now your prompts behave inconsistently.
How the Tool Registry Solves This
Define once, use everywhere. Create a tool in the registry, then add it to any prompt as a reference. Your prompts store a lightweight pointer — the actual definition is resolved at runtime from the registry.Tool Schema as a Contract
A tool’s function schema defines what the LLM can call — the function name, its parameters, and their types. Changing a schema changes LLM behavior. The Tool Registry treats schemas as versioned contracts:- Every edit creates a new immutable version with a commit message
- You can diff any two versions side-by-side to see exactly what changed
- The full version history gives you an audit trail of every contract change
- Release labels (like “production”) let you control which version is live
Know What will Break
The References tab on each tool shows exactly which prompts use it. Before changing a parameter or deleting a tool, you can see the blast radius:- Which prompts reference this tool
- Which labels they use
- How many are affected


