Skip to main content
Glama

List country shapes

list_countries

Find countries available for country-shaped mazes. Filter by name, code, or continent to select a country outline for maze generation.

Instructions

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 observedv1.0.1

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations at all, the description carries the full behavioral burden. 'List' implies a read-only, non-destructive operation, but nothing is said about result size, ordering, pagination, or what happens when filters match nothing. It does supply meaningful behavior via the enumeration of valid continent values, which the schema lacks.

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 purpose front-loaded, followed by filter semantics. No filler, no restatement of the tool name.

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 simple, two-optional-parameter read tool with no output schema, the description covers purpose and both parameters adequately. The main omission is any hint of return shape or result volume, which is a minor gap for a list operation.

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 0% — both parameters are bare untyped-to-semantics strings — so the description does real work: 'query' is defined as a partial match on 'part of a name or code', and 'continent' is given a concrete value list. Residual gaps remain (case sensitivity, exact spelling of 'North America'), keeping it below 5.

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?

States a specific verb ('List') and a precisely scoped resource ('countries available for country-shaped mazes'), which is clearly distinct from siblings like generate_maze or find_printable_mazes. It does not explicitly name a sibling to route against, 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?

Usage is implied by the enumeration nature of the tool, and the description explains how filtering works, but it gives no explicit when-to-use/when-not guidance or prerequisites. An agent can infer this is a discovery step before generate_maze, yet that inference is left to the caller.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools