Skip to main content
Glama

Coline

Get mail send status

get_mail_send_status
Read-onlyIdempotent

Checks whether an email from send_mail or reply_to_mail was approved and sent.

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": {
      "workspace": "<workspace>",
      "sendId": "<sendId>"
    },
    "name": "get_mail_send_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
sendIdYes
workspaceYesWorkspace slug from workspaces.list, e.g. "acme".

Output Schema

NameRequiredDescriptionDefault
toYes
fromYes
stateYes
sendIdYes
statusYes
messageYesNever say the mail was sent unless status is sent.
subjectYes
approvalUrlYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds real context the annotations lack — that the email is gated by an approval step before being sent — but says nothing about polling cadence, terminal states, or what happens for a send id that was rejected.

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 front-loaded sentence with no filler; the origin tools are named inline rather than in a separate clause, so nothing can be trimmed without losing meaning.

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?

With an output schema present, return-value explanation is not required, and the annotations carry the safety profile. Still, for a status-check tool with an undocumented sendId, the definition should say where the id comes from and whether the call is meant to be repeated until a terminal state.

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 50%: workspace is well documented in the schema, while sendId has no schema description. The description indirectly indicates where sendId comes from by referencing send_mail and reply_to_mail, but never states explicitly that sendId is the identifier returned by those tools, so the gap is only partially closed.

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?

States a specific verb and resource ("Checks whether an email ... was approved and sent") and anchors the resource to the tools that produce it (send_mail, reply_to_mail), which separates it from the sending siblings. It stops short of naming the status fields returned, but the scope is unambiguous.

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

Usage Guidelines3/5

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

Implicit guidance only: the mention of send_mail/reply_to_mail tells the agent this is the follow-up call after initiating a send. There is no statement about when not to call it, whether it should be polled, or what to do before approval completes.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources