Skip to main content
Glama
agentisend

agentisend

Why was this not sent?

why_was_this_not_sent
Read-onlyIdempotent

Identify what is blocking an email send for a specific message ID, or check current key and account blockers when no ID is provided.

Instructions

Purpose: find out what is holding a send. Name an email_id for one message, or omit it to ask what is blocking this key and this account right now. NOT for: the outcome of a delivered message (get_email) or what to do about a bounce (explain_email). Returns: every blocker, each with why, the fix, and is_normal_wait — the field that matters, because a scheduled send and a paused key look identical without it. When nothing is blocking, it says so and says what it checked rather than implying a message exists.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "why_was_this_not_sent"
  }
}

Input Schema

NameRequiredDescriptionDefault
email_idNoA message id. Omit to ask what is blocking this key generally.

Output Schema

NameRequiredDescriptionDefault
errorNoPresent instead of the fields above when the call was refused: code, message, fix, docs_url, retryable and, when waiting helps, retry_after_seconds.
scopeNoone_message or this_key.
statusNo
blockedNo
blockersNo
email_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), but the description adds real semantics beyond that: the significance of is_normal_wait (scheduled send vs. paused key look identical without it) and the empty-state behavior (it says what it checked rather than implying a message exists). That edge-case disclosure is exactly the kind of context annotations cannot carry.

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?

Labeled sections (Purpose / NOT for / Returns) keep it front-loaded and scannable, and every clause carries information. It is somewhat long for a one-parameter tool, particularly the Returns paragraph, which overlaps with the output schema, but nothing is padded or redundant.

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?

For a single optional param with an output schema, this is more than sufficient: invocation branching, exclusions, the key differentiating field, and the no-blocker case are all covered. An agent has everything needed to call it correctly and interpret the result.

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

Parameters4/5

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

Schema coverage is 100% for the single optional param, so the baseline would be 3, but the description adds meaning the schema lacks: the omitted-param path is characterized as "what is blocking this key and this account right now" rather than the schema's vaguer "this key generally." It clarifies the time-scope semantics of the zero-arg call.

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 diagnostic purpose ("find out what is holding a send") with a clear verb+resource framing, and explicitly distinguishes itself from two named siblings (get_email, explain_email). An agent can pick this over those tools without opening any schema.

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?

Gives the exact invocation branch (name an email_id for one message, omit it for an account/key-level check) and names the alternatives it is NOT for, plus the condition that selects them (delivered outcome vs. bounce remediation). Nothing is left to inference.

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