Skip to main content
Glama
yahoo-mail

yahoo-mail

by soothslayer

send_status

Read-onlyIdempotent

Look up the persisted outcome of an email send to confirm whether it succeeded, failed, or is unknown. Reconcile unknown results before resending to avoid duplicate messages.

Instructions

Look up the persisted outcome of a send. unknown must be reconciled before any resend.

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": {
      "idempotency_key": "<idempotency_key>"
    },
    "name": "send_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
idempotency_keyYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds genuine value by explaining the terminal "unknown" state must be reconciled before resending, which annotations cannot express. However, it doesn't say how long results are persisted, whether lookups can miss, or what other states exist besides unknown.

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

Conciseness4/5

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

Two short sentences, front-loaded with the purpose, with no padding. The second sentence is terse to the point of near-cryptic ("must be reconciled" by what mechanism?), but every sentence attempts to earn its place.

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?

For a one-parameter read tool with no output schema, the definition covers the safety context and the key reconciliation rule. It omits the most operationally important facts: how to obtain the idempotency key, what the returned state values are, and what to do when the outcome is still unknown.

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 the single required idempotency_key parameter, so the description must carry the meaning and it doesn't mention the key at all. An agent is left to infer that the idempotency key is the lookup handle and where it comes from (presumably the original send call).

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

Purpose3/5

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

"Look up the persisted outcome of a send" gives a specific verb and resource, but the scope is ambiguous: it doesn't say this is keyed by an idempotency key nor how it differs from siblings like send_message or search_messages. An agent can guess it retrieves send state, but not with confidence about what a "send" is in this system.

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

Usage Guidelines2/5

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

The second sentence implies usage (reconcile unknown results before resending) but states no explicit when-to-use versus alternatives, no prerequisites, and no guidance on whether it should be polled after every send or only on failure. The only exclusion is implicit in "before any resend".

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