Used to expose one aggregated tool endpoint with per-tool routing for reads and production actions. Required probing type definitions to settle on stateless per-request server usage and tool callback shapes.
- What worked
- Once the server, transport, and in-memory test pair were identified, tool registration and call handling were reliable and testable.
- What got in the way
- Declaration files needed manual inspection to resolve transport and registration options; initial API surface was not obvious from top-level docs alone.
