Skip to main content
Glama

check_delivery_status

Look up a sent message by message_id to report its delivery status, whether test delivery was real or sandbox, and the full event timeline.

Instructions

Look up a sent message by message_id (returned by send_test_otp) and report its status (queued, sent, delivered, opened, failed, bounced), whether test delivery was real or sandbox, and the event timeline.

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": {
      "message_id": "<message_id>"
    },
    "name": "check_delivery_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
message_idYesThe message id, as returned by send_test_otp.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It does real work by disclosing the possible status values (queued, sent, delivered, opened, failed, bounced), the real-vs-sandbox distinction, and the presence of an event timeline. It does not state that the call is a side-effect-free read, whether status is a live snapshot or eventually consistent, or what happens for an unknown or expired message_id.

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?

A single dense sentence that front-loads the verb and key input, then lists the returned information. Every clause carries information (input source, status set, sandbox flag, timeline) 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 single-parameter read tool with no annotations and no output schema, the description covers both the lookup mechanics and the shape of the response well enough to call it correctly. Residual gaps are polling/consistency guidance and error behavior on an invalid message_id.

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?

Only one parameter exists and schema description coverage is 100%, so the schema already explains message_id. The description restates the same fact ('returned by send_test_otp') without adding format, validation, or failure semantics beyond it, which is the expected baseline here.

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 gives a specific verb and resource ('look up a sent message by message_id') and enumerates exactly what is reported: status values, real-vs-sandbox delivery, and event timeline. It also ties the parameter to its producer (send_test_otp), which separates it from the send/recipient siblings. It stops short of naming a sibling it should be preferred over, so it is clear but not maximally differentiated.

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?

Usage context is clear: this is the follow-up to send_test_otp, since the message_id comes from that call, and the tool reports delivery progress rather than sending. There is no explicit 'do not use for X' exclusion or guidance on when to poll versus wait, which keeps it below a 5.

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