Skip to main content
Glama

Tips for a readable fax and cover sheet

get_fax_tips
Read-onlyIdempotent

How to make a document print clearly on a fax machine and what to put on a cover sheet. Read-only; general guidance, no personal data.

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_fax_tips"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the description's 'Read-only' clause merely repeats structured data. The one genuine addition is 'general guidance, no personal data,' which tells the agent the content is safe, non-sensitive boilerplate — a modest but real value-add.

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?

Two short sentences, front-loaded with what the guidance covers. Minor waste: the 'Read-only' clause duplicates annotation data, and the phrasing is descriptive rather than action-oriented, but nothing is bloated.

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 parameterless, non-mutating advisory tool with no output schema, this is nearly complete — it says what the content is about and that it contains no personal data. A sentence on the shape of the answer (e.g., prose tips) would close the last gap.

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?

The tool takes zero parameters, which is the baseline-4 case; there is nothing for the description to disambiguate. The schema definition itself is empty, so no coverage gap exists.

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 names the resource (fax readability guidance and cover-sheet content) concretely enough that an agent knows it returns advisory text rather than fax status or numbers. It stops short of explicitly contrasting itself with siblings like get_country_fax_guide, so it lands at clear-but-undifferentiated.

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 only implied: an agent can infer this is a reference/informational lookup, but the description never says when to call it (e.g., before drafting a fax, or when a user asks how to format a cover sheet) versus when to use get_country_fax_guide or get_fax_status. No exclusions or prerequisites are stated.

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