Skip to main content
Glama

List country shapes

list_countries

List the countries available for country-shaped mazes. Filter by part of a name or code, or by continent (Africa, Asia, Europe, North America, South America, Oceania, Antarctica).

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
queryNo
continentNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the burden. The verb 'List' reasonably conveys a read-only, side-effect-free query, but the description does not state result size, ordering, pagination, or matching behavior (case sensitivity, partial vs exact match) beyond the phrase 'part of a name or code'.

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 core purpose front-loaded and the filter options following. No filler, no restatement of the name or title.

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 two-optional-parameter enumeration tool with no output schema, the description covers the essential ground: what is listed and how to narrow it, including the exact continent vocabulary. The only gaps are result ordering and filter-combination semantics, which are minor at this complexity.

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 description coverage is 0%, so the description must compensate and largely does: it maps 'query' to matching part of a name or code and 'continent' to a fixed enumerated list (Africa, Asia, Europe, North America, South America, Oceania, Antarctica) that the schema does not contain at all. It does not clarify whether the two filters are combined or mutually exclusive.

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 gives a specific verb and resource — 'List the countries available for country-shaped mazes' — which is far more informative than the bare name. It implicitly separates itself from generate_maze and find_printable_mazes by being a pure enumeration of country options, though it never names those siblings.

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 implied rather than stated: the agent can infer this is the tool to call when it needs a country name or code to feed into a country-shaped maze. There is no explicit when-not guidance, no note on whether filters combine with AND/OR, and no mention of what to do when no match is returned.

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.