Skip to main content
Glama

Pay for and send a fax

send_fax
DestructiveIdempotent

Consequential paid action: charge $4 of Edwyna credit and queue one prepared fax for external transmission. The same fax ID is idempotent.

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

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 declare openWorld, destructive, and idempotent, but the description adds information they cannot carry: the exact $4 charge against Edwyna credit, that transmission is external, and that idempotency is keyed on the fax ID specifically. It does not cover failure/refund behavior or whether a balance check happens, so it stops short of 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two tight sentences with the highest-stakes fact ('Consequential paid action') front-loaded and the idempotency note second. Nothing is padded or redundant.

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 paid mutation with no output schema, the description covers cost, external side effect, and retry safety, which is most of what an agent needs before invoking. The remaining hole is provenance of fax_id and post-failure handling, but given the low tool complexity this is close to complete.

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 description must carry fax_id meaning, and it does partially by framing fax_id as the idempotency key. It still never says where fax_id originates (presumably prepare_fax) or what a malformed/nonexistent ID does, leaving a real gap for a single required parameter.

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?

States a precise verb pair ('charge $4 of Edwyna credit and queue one prepared fax for external transmission') plus the exact resource and cost, which cleanly separates it from get_fax_status, list_faxes, and prepare_fax. The phrase 'prepared fax' signals this is the send step after preparation, not the preparation itself.

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?

'Queue one prepared fax' implies the precondition that the fax must already exist from a prepare step, and 'consequential paid action' warns the agent this spends money. However, it never explicitly says to call prepare_fax first, never mentions checking balance or pricing, and gives no when-not-to-use condition.

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