Skip to content
amends

@amends-dev/toolkit

Tools from MCP servers and HTTP APIs in one shape, assembled into the toolkit an agent calls, with search and code mode to present many tools as few, and the conformance suites each source runs.

Each module’s page lists its exports by category, with their signatures and examples. The guide shows how the parts fit together.

  • Assembly: An assembly is the one toolkit a model is given for a turn, made of the tools of every source a workspace has.
  • CodeMode: Code mode presents a toolkit to a model as one tool, execute, which runs code the model writes.
  • Http: An HTTP API as a tool source.
  • Mcp: An MCP server as a tool source, reached over Streamable HTTP with an HTTP client the caller has already given the credentials the server asks for, so no credential enters this package.
  • OpenApi: readOperations makes the operations Http runs from the specification of an HTTP API, which is an OpenAPI 3 document read as JSON.
  • Presentation: What the ways to present a toolkit to a model share, such as ToolSearch and CodeMode.
  • ToolDefinition: A tool definition is a tool as data.
  • ToolSearch: Search is a way to show a model a large set of tools, or one that changes from turn to turn.
  • ToolSource: A tool source is a system that tells which tools it has and runs them, such as an MCP server or an HTTP API.
  • ToolSourceError: Errors a tool source reports when it cannot do what it was asked.
  • conformance/Fixture: What a tool source gives the conformance suites.
  • conformance: The test suites every kind of tool source runs against itself, so that code written against ToolSource works the same on each.