Skip to main content
Glama

Agent Bits

by dev.agentbits

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.5/5.0
Behavior4/5

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

No annotations exist, so the description carries full burden. It discloses the output metadata categories and the input requirement. It does not cover edge cases like case-insensitivity or errors, but for a simple read-only lookup the behavior is sufficiently transparent.

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 concise, front-loaded with the primary purpose, and uses clear sections for use/non-use. Every sentence earns its place.

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?

For a simple lookup tool with full schema coverage and no output schema, the description adequately explains what it does, when to use it, and what it returns. No gaps remain.

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 documents the parameter with pattern and examples. The description adds the same examples (CA, US, JP) but no additional meaning beyond the schema's 100% coverage. Baseline 3 applies.

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 resolves ISO 3166-1 alpha-2 codes to official name, region, currency, calling code, languages, and related metadata. It uses a specific verb (resolve) and resource (country code) and is differentiated from sibling tools via the 'Do not use when' section.

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?

Provides explicit 'Use when' scenarios with example queries, and 'Do not use when' conditions that name alternative tools (countries_bulk, currency_lookup). This fully guides selection vs alternatives.

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.1/5.0
Disambiguation5/5

Each tool targets a distinct data format and operation, with explicit 'Do not use when' cross-references to prevent confusion. For example, base64_encode/decode, url_encode/decode, and timestamp_convert/timezone_convert are clearly separated, and the various validators (ISBN, Luhn, UUID, JSON) apply to different identifiers.

Naming Consistency4/5

Most tool names follow an object_operation pattern (e.g., base64_decode, country_lookup, timestamp_convert), using lowercase with underscores. The main deviation is countries_bulk, which uses a noun+adjective form without an explicit operation, making it inconsistent with the verb-like operations used elsewhere.

Tool Count3/5

With 18 tools, the server falls into the 16-25 range which feels heavy for a utility collection. While each tool is individually useful and the scope is broad, the count is higher than typical for a well-focused server and may overwhelm agents scanning the available options.

Completeness4/5

The set provides solid coverage of encoding/decoding, validation, lookups, and conversions, with paired encode/decode and convert functions. However, some common utilities such as hashing, HTML entity encoding, UUID generation, or email validation are absent, leaving minor gaps for agents that need those operations.

Resources