Skip to main content
Glama

How to fax a country

get_country_fax_guide
Read-onlyIdempotent

How to write a fax number for a country FaxUp reaches, with the leading-0 rule, which numbers are mobiles, the time zone, and a link to the full guide. 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": {
      "country": "<country>"
    },
    "name": "get_country_fax_guide"
  }
}

Input Schema

NameRequiredDescriptionDefault
countryYesCountry name or ISO code, e.g. "Germany" or "DE".

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover safety (readOnlyHint, idempotentHint, destructiveHint=false), and "Read-only." merely restates that. What does add value is the disclosure of the returned content — formatting rule, mobile flag, time zone, guide link — since no output schema exists to describe it.

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 front-loaded sentence that lists the returned fields, with no filler. The comma-separated field list makes it slightly dense but each clause carries information.

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 single-parameter lookup with full schema coverage and no output schema, the description sufficiently describes what comes back and that the operation is read-only. The one gap is not stating what happens when a country is unsupported.

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 100%, so the country parameter is already documented with format examples. The description's only added meaning is the implicit constraint that the country must be one "FaxUp reaches," which is a marginal but real contribution; baseline 3 applies.

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 a specific resource and enumerates the payload: the leading-0 rule, mobile identification, time zone, and a link to the full guide. It does not explicitly distinguish itself from the sibling format_fax_number, which is the closest overlap, so it stops 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?

"for a country FaxUp reaches" implies usage is limited to supported countries, giving implicit scoping. There is no explicit when-to-use versus format_fax_number or list_supported_countries, and no stated behavior for unsupported input, so guidance is only implied.

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