> For the complete documentation index, see [llms.txt](https://docs.podigee.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.podigee.com/documentation/start-here/ai-agents/mcp-reference/common-tool-request-and-response-format.md).

# Common tool request and response format

Tool-call envelopes, structured results, annotations, controls, and public identifiers.

## Tool call

Use the MCP `tools/call` method with a registered tool name and an `arguments` object that matches the tool's input JSON Schema.

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "get_me",
    "arguments": {}
  }
}
```

Modern requests also carry the required protocol version and routing metadata described in the endpoint reference.

## Structured result

Successful tool calls return structured content that matches the published `outputSchema`. Clients should validate the structured result before they act on it. Do not infer undocumented fields.

## Annotations

Every tool advertises `readOnlyHint`, `destructiveHint`, `idempotentHint`, and `openWorldHint`. Annotations describe behavior but do not grant permission or replace the tool's scope mapping.

## Mutation controls

* `dry_run: true` requests a preview where supported.
* `confirm` carries the opaque confirmation returned by that preview.
* `idempotency_key` identifies one intended mutation where the schema requires it.

Do not alter a confirmation, parse it, or reuse it for another request.

## Identifiers

Podcast, episode, production, listener, asset, report, and import IDs are integers. Durable operation and upload IDs are UUID strings. Provider storage keys, multipart IDs, and credentials are not public identifiers.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.podigee.com/documentation/start-here/ai-agents/mcp-reference/common-tool-request-and-response-format.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.