reference-data-mcp-server

Country Search

ref_geo_search

Read-only

Search and filter countries by region, subregion, language, currency, or free-text keyword. At least one filter is required. Returns a ranked list of matching country summaries. Use ref_geo_lookup to get the full record for a specific result.

Input Schema

TableJSON Schema

Name	Required	Description
`limit`	No	Maximum number of results to return (1–100).
`region`	No	Filter by continent region: Africa, Americas, Asia, Europe, Oceania, or Antarctic.
`keyword`	No	Matches against country name, native name, capital city, and subregion.
`currency`	No	ISO 4217 currency code (e.g., "EUR") or currency name (e.g., "Euro").
`language`	No	ISO 639-1 language code (e.g., "pt") or language name (e.g., "Portuguese").
`subregion`	No	Filter by subregion (e.g., "Western Europe", "Southeast Asia", "South America").

Output Schema

TableJSON Schema

Name	Required	Description
`error`	No	Present when the call failed. Absent on success.
`notice`	No	Recovery hint when no countries matched — echoes active filters and suggests how to broaden.
`results`	No	Matching country summaries, up to limit.
`truncated`	No	True when totalMatches exceeds the limit and results are cut off.
`totalMatches`	No	Total countries matching the filters before limit is applied.
`appliedFilters`	No	Active filters applied to the search.

Schema Changelog

Changes observed during successful MCP inspections.

First observedSep 20, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds meaningful behavioral context: at least one filter must be supplied, results are ranked, and returns are summaries rather than full records. It does not explain the ranking criteria, but this is a minor gap.

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 three sentences with no redundant phrasing. The essential constraint 'At least one filter is required' appears early, and the pointer to ref_geo_lookup is concise and useful.

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 has an output schema, so return values need not be described in detail; the description still notes that results are summaries and ranked. The 'at least one filter' constraint and lookup pointer cover the main usage context. A slight gap is the unspecified meaning of 'ranked,' but overall the description is complete enough for selection and invocation.

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 description coverage is 100%, so all six parameters are already well documented. The description enumerates the filter dimensions but adds no new meaning beyond the schema's parameter descriptions. 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 searches and filters countries by multiple dimensions and returns a ranked list of summaries. It explicitly contrasts itself with ref_geo_lookup, which fetches the full record, making the tool's distinct purpose obvious.

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 states that at least one filter is required, indicating when the tool is appropriate, and explicitly directs users to ref_geo_lookup for full records. This provides clear routing between sibling tools.

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

All reference-data-mcp-server tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.