Skip to main content
Glama

Superpass

List countries

list_countries
Read-onlyIdempotent

Use this when the person asks which countries Superpass covers, or you need a country's code for get_chip_location. Give words to find a country by name. Not for one country's details: use get_chip_location. Answers the countries Superpass has researched, each with its code, its name and where the chip is in its passport in a few words; only the ones whose name has the words, when given.

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

Input Schema

NameRequiredDescriptionDefault
wordsNowords of a country's English name, or its two-letter code

Output Schema

NameRequiredDescriptionDefault
countriesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive and closed-world, so the safety profile needs no restating. The description adds genuinely new behavior: results are limited to researched countries, the filter is a substring match on the name, and omitting it returns the full set. The return-shape sentence ('each with its code, its name and where the chip is in its passport') partially duplicates the output schema, which keeps this from 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.

Conciseness4/5

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

Usage guidance is front-loaded and there is little wasted text, but the final sentence is a run-on held together by semicolons and the clause 'only the ones whose name has the words, when given' is syntactically strained. It could be split for faster parsing without losing content.

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?

With one optional parameter, full schema coverage, a complete annotation set and an output schema, the description covers everything still needed: purpose, alternative, filter semantics, and which countries appear in results. No call-blocking gap remains.

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% and the parameter is already documented as 'words of a country's English name, or its two-letter code', so the baseline is 3. The description earns an extra point by clarifying that the filter is optional and that omitting it yields all countries — semantics the schema alone does not convey. It does, however, describe matching as on 'name' only, which sits awkwardly with the schema allowing a two-letter code as input.

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?

Names a specific verb and resource ('which countries Superpass covers', 'answers the countries Superpass has researched') and explicitly distinguishes itself from get_chip_location, so an agent can route without opening either schema. The scope restriction to 'researched' countries is stated outright.

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 both the trigger ('when the person asks which countries Superpass covers, or you need a country's code for get_chip_location') and the exclusion ('Not for one country's details: use get_chip_location'), naming the alternative tool and the condition that selects it.

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