Inbox Triage

Load the whole email for the inbox view

get_message_html

Read-onlyIdempotent

Used by the interactive inbox view to show a message the way the sender designed it. Returns sanitized HTML for a sandboxed frame; remote images stay off unless allowImages is true. Agents should call get_message.

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>",
      "messageId": "<messageId>"
    },
    "name": "get_message_html"
  }
}

Input Schema

Name	Required	Description	Default
`inboxId`	Yes
`messageId`	Yes
`allowImages`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 26, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already cover safety profile (readOnly, idempotent, non-destructive, open-world). The description adds meaningful behavioral context: sanitized HTML for a sandboxed frame and remote images staying off unless allowImages is true. It doesn't discuss error modes or auth, but those are less critical here.

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?

Three sentences, front-loaded with purpose and behavior, then a clear routing instruction. Every sentence adds value with no redundancy.

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

Completeness3/5

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

Given a simple tool with no output schema and annotations covering safety, the description is mostly adequate. However, with 0% schema description coverage, it should explain the two required identifiers (inboxId, messageId) to be complete for invocation.

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

Parameters2/5

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

Schema description coverage is 0% for all three parameters. The description only explains allowImages ('remote images stay off unless allowImages is true'), leaving the required inboxId and messageId entirely undocumented. Two of three parameters lack any semantic explanation.

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?

States a specific verb ('Returns') and resource ('sanitized HTML' of a message), and explicitly distinguishes itself from the sibling get_message tool by directing agents there. An agent can tell exactly what this tool does and does not do.

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

Usage Guidelines5/5

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

Explicitly sets the usage context ('interactive inbox view') and names the alternative for agents ('Agents should call get_message'). This provides clear when-to-use and when-not-to-use guidance without inference.

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?