AGT-02 · Tool registry: define, secure, change and operate tools¶
Each project defines tools differently, so schemas drift, errors are unreadable to the model and nobody knows which agent can call which tool. Credential rotations and schema changes then break agents in production without warning.
- Who reads it: GenAI engineers who write tools and DevOps and security engineers who run and govern them
- Outcome: Versioned, permissioned tools with zero-surprise changes and rotations
- Pack owner: James (catalog owner role: Agent Lead)
Master catalog entry¶
- Catalog name: Tool Calling & Function Registry Framework (P1)
- Why it matters: Tool sprawl is the main reason agent projects become unmaintainable
- What it removes: Schema generation, validation, auth and error contracts standardised
- Stack: Python, Pydantic, OpenAPI, MCP, LangGraph
- Maturity target: Level 3 — registry with versioning and per-tool permissioning
Playbooks¶
| ID | Story | Title | Kind | Complexity | Urgency | Status | Owner | Planned publish |
|---|---|---|---|---|---|---|---|---|
| PB-AGT-02-01 | AGT-02-S1 | Define a tool with Pydantic schemas, an error contract and a registry entry | How-to | Medium | 3 | draft | Sanjay Sarvesh | 2026-12-08 |
| PB-AGT-02-02 | AGT-02-S2 | Rotate credentials for MCP servers and tool connectors without downtime | Runbook | Medium | 5 | draft | James | 2026-10-30 |
| PB-AGT-02-03 | AGT-02-S3 | Ship a breaking tool schema change with versioning and canary | Runbook | High | 4 | draft | James | 2026-11-24 |
| PB-AGT-02-04 | AGT-02-S4 | Tool security and per-tool permission review | Checklist | Medium | 4 | draft | Sanjay Sarvesh | 2026-11-18 |
| PB-AGT-02-05 | AGT-02-S5 | Handle a tool dependency outage or throttling | Runbook | Medium | 5 | draft | Sanjay Sarvesh | 2026-11-11 |