Skip to main content
Glama

Agent Bits

by dev.agentbits

currency_lookup

Resolve an ISO 4217 currency code such as USD, EUR, or JPY to its name, symbol, decimal places, and which countries use it when you need currency metadata rather than a live exchange rate.

Use when:

  • What is the symbol and number of decimal places for EUR?

  • Which countries use currency code JPY?

  • Get ISO 4217 name and metadata for USD

Do not use when:

  • Convert amounts between currencies or fetch live FX rates

  • Find which currency a country uses when you only have a country code (use country_lookup)

  • Validate payment-card-like numbers (use luhn_validate)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
codeYes

TDQS

A4.7/5.0
Behavior4/5

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

With no annotations provided, the description does the heavy lifting. It clearly discloses that the tool returns metadata and is not for live rates. It does not mention error handling or case sensitivity, but for a simple lookup this is adequate. It could go further, but it does not contradict anything.

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-structured with a clear lead sentence and organized use/do-not-use lists. Every sentence adds value, and it remains succinct despite covering alternatives.

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?

Given the tool's low complexity (one parameter, no output schema), the description fully covers purpose, usage, exclusions, and return content. It is complete for an agent to select and invoke correctly.

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?

The schema provides only min/max length for 'code' with 0% description coverage. The description compensates by giving examples (USD, EUR, JPY) and explaining the code's role as an ISO 4217 currency code, adding meaning beyond the schema.

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 4217 currency codes to metadata like name, symbol, decimal places, and countries, distinguishing it from exchange rate tools and sibling lookups. The verb 'resolve' is specific and the resource is well-defined.

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 and states alternatives like country_lookup and luhn_validate. This fully guides the agent on when to select this tool.

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