Expose business tools to agents with explicit permissions


In 30 seconds
Problem
An agent needs a controlled way to access business APIs without embedding customer identifiers or private operating instructions in every prompt.
My part
I implemented Python MCP tools for support integrations and built contract-derived skill references with shared confirmation rules.
Result
The implementation separates tool access, account context and distributable references from private source material.
Technical decisions
Pass account and conversation identifiers with the tool call.
- Why
- Support actions need the caller’s current context.
- Trade-off
- Inputs must be checked at the API boundary.
Generate references from published contracts.
- Why
- Hand-maintained copies drift when APIs change.
- Trade-off
- The generator needs pinned inputs, a manifest and checks on the distributable output.
Operation
The work includes MCP transport integrations, retry-aware API clients and checks for private terms before distributing generated references. Related client work uses incremental history mirroring and additive migrations with a read-only source.
Authorship
I contributed API integrations for a client and contract-derived skills for Conversa Labs, with account context and confirmation rules defined at the tool boundary.

