Skip to main content
Glama

Agent Bits

by io.github.rwaldman

country_lookup

Resolve an ISO 3166-1 alpha-2 country code (for example CA, US, JP) to official name, region, currency, calling code, languages, and related country metadata when you already have the two-letter code.

Use when:

  • What currency and calling code does country code JP use?

  • Get official name, region, and languages for ISO country CA

  • Look up standardized metadata for a two-letter ISO 3166-1 country code

Do not use when:

  • Download the full countries dataset for offline or multi-country use (use countries_bulk)

  • Look up currency symbol or decimals by ISO 4217 code alone (use currency_lookup)

  • Search for a country when you only know its English name and not the ISO code

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
codeYesISO 3166-1 alpha-2 country code, for example CA or JP

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations, the description takes on the full burden of explaining behavior. It details the output (official name, region, currency, calling code, languages, related metadata) and the input prerequisite (having the two-letter code). It does not explicitly cover edge cases like invalid or unrecognized codes, but the schema pattern addresses format validation, making this a minor gap. The description adds valuable behavioral context beyond the raw tool name.

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?

The description is well-organized with a clear purpose statement followed by bullet-point use cases and exclusions. It is front-loaded and every section earns its place, providing usage examples and alternatives without unnecessary fluff. The structure aids quick parsing by an AI agent.

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?

The tool is a simple one-parameter lookup, and the description is complete in scope: it lists the returned metadata categories, specifies the input format, and provides usage boundaries. While there is no output schema, the description compensates by enumerating the output fields. It omits details about error handling for nonexistent codes, but overall it is sufficient for an agent to decide when and how to invoke it.

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?

The schema already covers 100% of the parameter description, including the pattern and examples ('ISO 3166-1 alpha-2 country code, for example CA or JP'). The tool description reinforces this with examples and the context of 'when you already have the two-letter code,' but does not add substantial new semantics beyond the schema, so baseline 3 is appropriate.

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?

The description clearly states the tool's function: 'Resolve an ISO 3166-1 alpha-2 country code... to official name, region, currency, calling code, languages, and related country metadata.' It uses a specific verb (resolve) and resource (ISO code → metadata), and distinguishes it from siblings by noting it applies 'when you already have the two-letter code.'

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?

The description provides explicit 'Use when' and 'Do not use when' sections with concrete example queries. It names alternatives: countries_bulk for bulk/dataset needs and currency_lookup for ISO 4217 code lookups, offering clear guidance on when to choose this tool over siblings.

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

All Agent Bits toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.3/5.0
Disambiguation5/5

Each tool targets a distinct resource and action, with clear use cases and explicit 'Do not use when' guidance preventing confusion. For example, base64_decode and url_decode handle different encoding schemes, while timestamp_convert and timezone_convert address separate time operations.

Naming Consistency5/5

All tool names follow a consistent lowercase snake_case verb_noun pattern (e.g., base64_decode, country_lookup, uuid_validate). While verbs vary (decode, encode, lookup, validate, convert), the naming format is uniform and predictable.

Tool Count4/5

The 18-tool set is slightly above the typical 3-15 range, but the breadth is justified by the server's purpose as a general-purpose utility toolkit. Each tool earns its place, and the count does not feel overwhelming or redundant.

Completeness4/5

The toolkit covers encoding/decoding, validation, lookups, and conversions across common developer needs. Minor gaps exist, such as no UUID generation tool to complement uuid_validate, and no HTML entity encoding/decoding, but these are not critical omissions for the stated utility scope.

Resources