Inbox Triage

Get masked-form link for the mailbox password

start_imap_secret_capture

Returns a link to a masked form where the human enters an iCloud app-specific password or IMAP mailbox password. Show only sayToHuman + url in chat; never ask them to paste the password, and never paste inboxId/raw JSON. For Yahoo and AOL addresses, when sign-in is enabled on this server, it returns a sign-in link instead unless appPassword is true.

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

Input Schema

Name	Required	Description	Default
`inboxId`	Yes
`appPassword`	No	Yahoo/AOL only: use the app-password form even though sign-in is available.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 26, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already declare it is not read-only, not destructive, and open-world; the description adds meaningful behavior beyond that, including the masked-form flow, secret-handling rules, and Yahoo/AOL sign-in-link fallback. It still does not explain the side effect that makes readOnlyHint false or what state is created by starting the capture.

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 description is front-loaded with what the tool returns, then gives concise handling rules and the Yahoo/AOL exception. Each sentence carries distinct operational value with no filler.

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

Completeness4/5

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

For a tool with no output schema, the description explains the returned link, the sayToHuman + url display expectation, secret-handling constraints, and the Yahoo/AOL fallback. It is nearly complete, though it could clarify prerequisites or error behavior around inboxId.

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 only 50%, and the description adds useful semantics for appPassword by tying it to Yahoo/AOL and the sign-in-link alternative. However, inboxId remains undocumented in both the schema and the description beyond the warning not to paste it, so the description only partially compensates for the coverage gap.

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

Purpose4/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 returns a link to a masked form where a human enters an iCloud app-specific or IMAP mailbox password. It also covers the Yahoo/AOL conditional behavior, but it does not explicitly contrast itself with sibling OAuth tools like start_google_oauth or start_microsoft_oauth.

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 operational guidance: show only sayToHuman + url in chat, never ask the user to paste the password, and never paste inboxId or raw JSON. It also explains the Yahoo/AOL exception when sign-in is enabled unless appPassword is true, though it does not explicitly say when to choose this tool versus the OAuth siblings.

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?