Inbox Triage

Show a draft as a card

show_draft

Read-only

Shows a draft from create_draft as a card the person can read, edit, and send with a click. Pass the inboxId and the draft id from create_draft. Apps that cannot show cards (Claude Code and other terminals) get the draft as text with To, Subject, and body: show it to the person as it is. Sending then goes through send_draft (a Send, Edit, Cancel prompt in apps that can ask the person directly, or the approval page). Sample drafts show without a Send button. When the person sends from the card, you are told; do not send it again.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "inboxId": "<inboxId>",
      "draftId": "<draftId>"
    },
    "name": "show_draft"
  }
}

Input Schema

Name	Required	Description	Default
`draftId`	Yes	The id create_draft returned
`inboxId`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 26, 2026

TDQS

A4.5/5.0

Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already mark this as read-only and non-destructive, but the description adds substantial behavioral context beyond them: card vs. plain-text fallback, the Send/Edit/Cancel prompt or approval page, sample-draft behavior, and the instruction not to resend after the person sends from the card. This is rich operational detail that helps an agent invoke and interpret the tool correctly.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose is front-loaded, and every sentence carries useful information: parameter source, fallback rendering, sending flow, sample-draft exception, and the no-double-send rule. There is no filler or repetitive restatement.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description covers the relevant return/display behavior (card vs. text, To/Subject/body), the sending handoff, and post-send notification. Combined with annotations that already establish the read-only safety profile, this is complete enough for correct invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 50%: draftId is documented as the id create_draft returned, while inboxId has no schema description. The description reinforces that draftId comes from create_draft and says to pass inboxId, but it does not add meaning about what inboxId represents or where to obtain it.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource: it shows a draft (from create_draft) as a card the person can read, edit, and send. It clearly distinguishes itself from siblings like create_draft and send_draft by explaining that it renders the draft and that the actual sending goes through send_draft.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives clear context: pass inboxId and the draft id from create_draft, and sending then goes through send_draft. It also explains the fallback for apps that cannot show cards and notes that sample drafts show without a Send button, though it does not explicitly exclude other uses or name every alternative.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Inbox Triage tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?