Skip to main content
Glama

Check a fax request

get_fax_status
Read-onlyIdempotent

Status of a prepared fax request: awaiting_confirmation, opened, handed_off (taken to faxup.net to send), cancelled, or expired; once the person has sent it on FaxUp, its delivery (sending, delivered or failed). Read-only.

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_request_id": "<fax_request_id>"
    },
    "name": "get_fax_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
fax_request_idYesThe fax_request_id of the prepared fax.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / fax_request_id / description
      Previous value: -"The fax_request_id send_fax returned."New value: +"The fax_request_id of the prepared fax."
  2. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so safety is covered; the description adds real value by disclosing the state machine and clarifying that delivery status (sending/delivered/failed) only becomes visible after the person sends it on FaxUp. The trailing 'Read-only' mostly duplicates the annotation, which keeps it from a 5.

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?

It is a single densely packed sentence that leads with the resource and then enumerates states, so nothing is buried. The semicolon-chained state list is readable but slightly cramped, and 'Read-only.' adds nothing beyond the annotations.

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 one-parameter read tool with no output schema, the description supplies the key missing piece: the set of possible status values and what they mean. It does not discuss polling cadence or how the ID is obtained, which would be the last 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?

With a single parameter at 100% schema description coverage, the schema already carries the semantics. The description only adds that the ID refers to a 'prepared' fax request, a minor gloss beyond the schema's own text.

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 clearly identifies the resource (a prepared fax request) and what it returns (its lifecycle status), listing concrete state values so the agent knows the shape of the answer. It does not explicitly contrast with siblings like send_fax or get_price_quote, so it falls short of a 5.

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: given a fax_request_id for a prepared request, this returns where it stands. There is no explicit instruction on when to call it versus other tools, nor any stated preconditions or exclusions, leaving the agent to infer the trigger conditions.

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