List every country Quantamentry scores, in rank order by composite sovereign-credibility score, plus the 'monitored' countries held out of the headline ranking for thin data coverage. Free tier: credibility BAND only, no composite scores and no deltas. Call get_country for a single country's score.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description must carry the behavioral disclosure. It explains the free-tier limitation (credibility band only, no composite scores or deltas) and the treatment of thin-data monitored countries. This is meaningful behavioral context, though it could have been slightly more explicit about output shape or ordering behavior.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is compact, with no filler. The first sentence delivers the core purpose and ranking, the second adds the tier limitation, and the third points to a sibling tool. Every sentence earns its place and the structure is front-loaded.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a zero-parameter listing tool with no output schema, the description covers purpose, order, exclusions, tier constraints, and the correct alternative for single-country data. There is no missing information an agent would reasonably need to invoke or interpret this tool.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The tool takes zero parameters, so schema coverage is complete by definition. The description adds no parameter-specific detail because there are none; the baseline of 4 applies. It still informs what the output will contain, which is relevant to expected usage.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description states a specific verb ('List') and resource ('every country Quantamentry scores'), adds the ranking criterion and explicitly calls out the monitored-country exception. It is easily distinguishable from get_country (single country) and get_latest_briefing (briefing), so an agent can select it without opening the schema.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description clearly indicates when to use the tool: when you need the full list of countries in rank order. It also points to the alternative get_country for single-country lookups, and qualifies the free-tier behavior. This gives an agent explicit routing guidance.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool targets a clearly distinct operation: one returns a single country's details, one returns the full ranked country list, and one returns the weekly briefing. There is no meaningful overlap or risk of an agent picking the wrong tool for a given task.
All tool names follow a predictable verb_noun pattern using get_ and list_, which are standard read-operation verbs in MCP tooling. The naming is consistent, lowercase, and makes the purpose of each tool immediately clear.
Three tools is a well-scoped size for a focused sovereign-credibility data server. Each tool provides a distinct, necessary capability—single-country lookup, full list, and latest briefing—without redundant or excessive surface area.
For a read-only public data service, the surface covers the core workflows: listing available countries, retrieving a single country's score, and reading the latest weekly briefing. The noted free-tier limitations are explicit constraints rather than missing operations an agent would expect from this server.