inspect_tool

Read the current contract and worked example for one catalog tool.

View Markdown

inspect_tool shows the selected tool's inputs, outputs, current price and worked example. Inspect before every unfamiliar run.

Signature

code
inspect_tool({ tool_id })

The canonical field is tool_id, returned by search_tools. MCP accepts only tool_id; capability_id is not an input field.

code
{
  "name": "inspect_tool",
  "arguments": {
    "tool_id": "<tool_id returned by discover>"
  }
}

Return shape

The response contains the current public contract: identity and summary, price and unit, connection state, input schema, a human-verified worked_example when one exists, and common_errors. It also provides next_step and warnings when the connection or health needs attention.

code
{
  "id": "<catalog tool id>",
  "name": "<catalog tool>",
  "input_schema": { "type": "object" },
  "worked_example": {
    "input": { "<field>": "<example value>" },
    "output": { "<provider result>": "<redacted value>" }
  },
  "common_errors": [],
  "next_step": "Copy worked_example.input and call run_tool."
}

Any cost estimate in worked_example applies to that example; run_tool estimates the actual input you submit.

Do not copy a provider schema, price or worked example from this documentation. Those fields can change and belong to the live response.

Common errors and recovery

  • Missing tool_id: return to search_tools; ids are not guessed.
  • Unknown id: search again because the record may be unpublished, archived or no longer live.
  • Missing worked example: follow input_schema exactly and treat the call as higher risk.
  • requires_connection with connected: false: give the human the connect_url from the next run error.

Once the input is understood, continue to run_tool.

inspect_tool — Scrollport