Skip to main content
Glama

Get fax status

get_fax_status
Read-onlyIdempotent

Read the current delivery and financial status of one fax. Poll until delivered or failed; delivery typically takes 5–10 minutes and may take up to 45 minutes.

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": {
      "fax_id": "<fax_id>"
    },
    "name": "get_fax_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
fax_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent and non-destructive semantics, so the description correctly spends its words elsewhere: expected latency (5–10 minutes typical, up to 45 minutes) and the poll-to-terminal-state protocol. That timing context is genuinely useful for an agent deciding retry cadence, though the intermediate statuses it might observe are not listed.

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?

Two sentences, no filler, with the core action stated first and the polling/latency guidance second. Every clause carries operational value.

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?

There is no output schema, and the description at least names the two dimensions returned (delivery and financial status) plus the terminal states, which is enough for an agent to interpret a response. It stops short of enumerating the non-terminal statuses or the financial fields, a modest gap for a simple single-parameter status tool.

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 0%, so the schema supplies only the name and uuid format for fax_id, and the description adds nothing about where that identifier originates. The single required parameter is largely self-explanatory, which keeps this from being a serious defect, but low coverage leaves the sourcing of fax_id undocumented.

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?

Specific verb ("Read") plus a precisely scoped resource ("the current delivery and financial status of one fax"). The singular "one fax" implicitly separates it from list_faxes, but no sibling is named explicitly, so it falls short of full differentiation.

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?

It tells the agent to "poll until delivered or failed," giving both the calling pattern and the terminal conditions that end polling. It stops short of naming alternatives — e.g., that a fax_id must first come from send_fax or list_faxes.

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