Skip to main content
Glama

List recent faxes

list_faxes
Read-onlyIdempotent

List recent fax records, optionally filtered by delivery status.

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": "list_faxes"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
statusNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.8/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds nothing beyond that: no pagination behavior, no default/limit semantics, and "recent" is never defined as a time window, which is the one piece of behavior an agent actually needs here.

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 tight sentence with the scope and filter front-loaded and no filler. It is well-sized but underspecified rather than over-worded.

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?

For a simple two-parameter read-only list tool with annotations covering safety and no output schema, the definition is minimally viable. It still leaves the meaning of "recent" and the limit/pagination behavior entirely undefined, which an agent needs to call it correctly.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must carry parameter meaning, but it only alludes to the status filter and says nothing about the limit parameter, its default of 25, or its 1-100 range. The enum values for status are visible in the schema but their semantics are unaddressed.

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 ("List recent fax records") plus a scope qualifier ("recent") and filter capability, which distinguishes it from mutation siblings like send_fax and prepare_fax. It does not explicitly differentiate from get_fax_status, which an agent might confuse for a single-record lookup.

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

Usage Guidelines2/5

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

The only usage hint is "optionally filtered by delivery status," which is embedded in the description rather than framed as guidance. There is no statement of when to prefer this over get_fax_status or how far back "recent" reaches, leaving the agent to infer context.

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