countries

Countries By Currency

countries_by_currency

Read-onlyIdempotent

Find countries using a currency (e.g., "EUR" for Euro, "USD" for US Dollar). Returns name, capital, region, and currency details.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`currency`	Yes	Currency code or name (e.g. "eur", "usd", "dollar")

Output Schema

TableJSON Schema

Name	Required	Description
`count`	Yes	Total number of countries using the currency
`currency`	Yes	Currency code or name queried
`countries`	Yes	Countries using the currency sorted by name

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedMay 8, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "count": {
+      "description": "Total number of countries using the currency",
+      "type": "integer"
+    },
+    "countries": {
+      "description": "Countries using the currency sorted by name",
+      "items": {
+        "properties": {
+          "capital": {
+            "description": "Capital city or N/A if not available",
+            "type": "string"
+          },
+          "name": {
+            "description": "Common country name",
+            "type": "string"
+          },
+          "region": {
+            "description": "Geographic region",
+            "type": "string"
+          }
+        },
+        "required": [
+          "name",
+          "capital",
+          "region"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "currency": {
+      "description": "Currency code or name queried",
+      "type": "string"
+    }
+  },
+  "required": [
+    "currency",
+    "count",
+    "countries"
+  ],
+  "type": "object"
+}

Changed1 schema field changedMay 6, 2026

addedInput schema / examples

Added value: +[
+  {
+    "currency": "EUR"
+  },
+  {
+    "currency": "USD"
+  }
+]

First observedApr 14, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint false. The description adds value by listing the return fields (name, capital, region, currency details), which is not provided by annotations. It does not contradict any annotation.

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 a single concise sentence with clear purpose, examples, and return fields. It is well-structured, front-loaded with the verb, and every word serves a purpose.

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 single parameter, existing output schema, and rich annotations, the description covers all essential aspects: purpose, example inputs, and output fields. No critical information is missing for an agent to correctly invoke the tool.

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 input schema fully describes the 'currency' parameter with 100% coverage, including examples and accepted formats ('eur', 'usd', 'dollar'). The description's examples repeat the schema examples and add no new parameter semantics.

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 uses the specific verb 'Find' with a clear resource ('countries using a currency') and is easily distinguished from sibling tools like countries_by_language and countries_by_region. The examples (EUR, USD) further clarify the domain.

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?

The description implies when to use the tool (when needing countries for a given currency) but does not explicitly mention alternatives or provide exclusions. For instance, it does not say 'for countries by language, use countries_by_language'. Thus, it provides clear context but lacks explicit guidance relative to sibling tools.

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

All countries tools Inspect

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.