Skip to main content
Glama

List faxes

get_faxes
Read-onlyIdempotent

Use this when the person asks about faxes they've sent from their Faxette account, like what they sent last week or which faxes failed. Returns 25 at a time, newest first. Pass next_page back as page for the next 25. Filter with status, for example ["failed"] or ["delivered"]. Use get_fax for one fax's details. Needs the person to sign in to Faxette; calling it while they aren't asks the app to sign them in. It changes nothing.

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

Input Schema

NameRequiredDescriptionDefault
pageNoThe next_page from the previous call.
statusNoOnly faxes in these states.
organizationNoAn organization's id from get_organizations, to list the faxes its members sent. Leave it out for the person's own.

Output Schema

NameRequiredDescriptionDefault
faxesYes
next_pageYesPass it as page for the next 25. Null on the last page.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / organization
      Added value: +{
      +  "description": "An organization's id from get_organizations, to list the faxes its members sent. Leave it out for the person's own.",
      +  "minLength": 1,
      +  "type": "string"
      +}
  2. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description still adds real behavior: 25-item page size, newest-first ordering, the next_page round-trip, and the auth flow (sign-in is triggered if the person isn't authenticated). 'It changes nothing' merely restates the annotations but does not conflict with them.

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?

Front-loaded with the trigger, then pagination, filtering, the sibling alternative, and auth — every sentence carries usable information. The closing 'It changes nothing' is the one redundant line given readOnlyHint and destructiveHint are already set.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Output schema exists so return shape needn't be described; the description covers the remaining essentials for a paginated list tool: page size, ordering, paging loop, filtering, auth requirement, and the single-item alternative. Nothing an agent needs to invoke it correctly is missing.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, and the description earns an increment by explaining the page parameter as a next_page round-trip and by demonstrating filter syntax with example status values. It says nothing about the organization parameter, which the schema already documents.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Description states a specific verb+resource ('faxes they've sent from their Faxette account') and scopes it to outbound faxes, which implicitly separates it from get_inbound_faxes and get_fax. It also names get_fax for the single-record case, so an agent can route without opening any schema.

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

Usage Guidelines5/5

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

Gives concrete triggers ('what they sent last week or which faxes failed'), states the alternative ('Use get_fax for one fax's details'), and shows how to apply the status filter with example arrays. When-to-use and when-not-to-use are both explicit.

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.