Skip to main content
Glama

Caelara Labs Global Locale

country_iso_enricher

Resolve a country name or ISO code to alpha-2/alpha-3/numeric codes, currency, calling code, region, capital and primary timezone

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": {
      "q": "<q>"
    },
    "name": "country_iso_enricher"
  }
}

Input Schema

NameRequiredDescriptionDefault
qYesCountry name, alpha-2, alpha-3 or numeric code

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden. It implies a stateless read lookup and helpfully enumerates the return fields, which substitutes for the absent output schema. However, it says nothing about ambiguous input (e.g. a name matching multiple countries), invalid or unknown codes, or error behavior — real concerns for a resolver that accepts free-text country names.

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?

One sentence, front-loaded with the action and input, followed by the output payload. No filler and nothing an agent must read twice.

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 one-parameter stateless lookup with no output schema, the description successfully enumerates what comes back, which is the main completeness risk here. The remaining gap is failure/ambiguity handling, which is minor for a deterministic reference lookup but not covered anywhere else.

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 coverage is 100% and there is a single parameter whose schema description already enumerates the accepted forms (name, alpha-2, alpha-3, numeric). The description adds no syntax, format, or edge-case detail beyond that. Baseline 3 applies when the schema does the heavy lifting.

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 opens with a specific verb ('Resolve') and a concrete resource ('country name or ISO code'), then enumerates the returned attributes (alpha-2/alpha-3/numeric, currency, calling code, region, capital, timezone). That makes it clearly distinguishable from sibling utilities like 'timezone_converter' or 'live_fx_rates', which touch overlapping data but do different work. It stops short of explicitly naming a sibling it supersedes or complements.

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?

There is no explicit when-to-use or when-not-to-use statement and no named alternative. Usage is only implied by the field list: an agent infers it should call this when it needs country metadata for normalization or enrichment. For a single-purpose lookup that inference is easy, but the definition leaves routing to the caller.

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