Skip to main content
Glama

Check Letter Send Status

send_status

Check a send request: status (PENDING/SENT/REJECTED/FAILED), the key's trust tier and tier decision, approval state (+approval_url while pending), and billing state (Stripe charge id when billed).

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

Input Schema

NameRequiredDescriptionDefault
api_keyYesyour 3L-Group Technology API key (lms_...).
request_idYesthe request_id returned by request_send.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

The description adds real lifecycle context beyond annotations: it discloses that approval_url appears only while pending and that a Stripe charge id appears only when billed, which tells the agent the shape of state evolves. However, it describes returned fields that a dedicated output schema already covers, and it never addresses the notable tension that readOnlyHint=false and idempotentHint=false on a 'check' call imply possible side effects or repeated-call costs.

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?

A single sentence with the core action front-loaded and the interesting fields grouped in parentheses. Every clause carries information; nothing is padding, though the density of parenthetical detail makes it slightly harder to scan.

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 two-parameter, read-oriented status tool with an output schema present, the description supplies the state machine (PENDING/SENT/REJECTED/FAILED, approval, billing) an agent needs to interpret results. It does not need to restate return types, but a note on polling cadence or whether repeated calls have effects would close the remaining gap.

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 description coverage is 100%: api_key is documented as an lms_ key and request_id as the value returned by request_send. The description adds no parameter-level detail beyond what the schema states, so the baseline 3 is appropriate.

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 names a specific verb and resource ('Check a send request') and enumerates the facets returned: status enum, trust tier/decision, approval state, and billing state. This clearly separates it from siblings like get_fax_status and request_send, which operate on different resources. It stops short of a 5 only because it never explicitly names the sibling it complements.

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?

Usage is implied rather than stated: the request_id parameter and the mention of PENDING/approval state imply this is the polling call issued after request_send (and while approve_fax is pending). There is no explicit 'use when' or 'do not use for fax status – use get_fax_status instead' routing, so an agent must infer the sequencing.

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.