Skip to main content
Glama

List countries FaxUp can fax

list_supported_countries
Read-onlyIdempotent

Countries FaxUp can send faxes to, with their calling codes. Read-only.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so 'Read-only' in the description is largely redundant. The genuinely additive part is 'with their calling codes', which discloses the shape of the returned data even though no output schema exists — valuable for a tool whose output is otherwise undocumented.

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 fragments with the resource stated first and the returned content second — well front-loaded and free of padding. The only wasted words are 'Read-only', which just restates the annotations.

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 zero-parameter static reference list with no output schema, this is nearly sufficient: it says what is listed and what fields come back. A note on whether results are sorted/grouped or a pointer to get_country_fax_guide would close the remaining 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, so per the baseline this dimension sits at 4. The schema is empty and 100% covered; the description correctly makes no parameter claims and needs none.

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 (supported countries) and adds scope (where FaxUp can send faxes) plus returned content (calling codes). It is clearly distinguishable from action tools like send_fax, but it does not differentiate itself from the sibling get_country_fax_guide, which an agent could easily confuse it with.

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?

The read-only lookup framing implies when the tool is appropriate, but there is no explicit when-to-use statement, no prerequisite (e.g. call before send_fax to check coverage), and no exclusion pointing to get_country_fax_guide for per-country details.

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