Get one country's public sovereign-credibility reading: the 0-100 composite score, its credibility band, its rank and percentile within its region, the 7-day move, a one-line read and the score date. The seven underlying dimensions, the executive summary and the 90-day history are not in the free tier.
| Name | Required | Description | Default |
|---|---|---|---|
| iso | Yes | ISO 3166-1 alpha-3 country code, e.g. 'BRA'. |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the behavioral disclosure burden. It explicitly names the returned fields and also states what is NOT available in the free tier (underlying dimensions, executive summary, 90-day history). This gives strong transparency about payload scope and tier limitations, though it doesn't discuss errors, auth, or data freshness beyond 'score date'.
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?
Two tight sentences. The first leads with the action and then enumerates the exact return fields in a colon-separated list; the second usefully states what is excluded. No filler or repetition of schema info.
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 single-param, no-output-schema tool, the description is effectively an output contract: it lists all returned components and explicitly flags excluded fields. An agent can select and call this tool with confidence on a first attempt.
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?
Schema coverage is 100% and the schema already fully describes the iso parameter with an example. The description adds no new parameter-level meaning, so it earns the baseline of 3 without needing to compensate.
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?
States a specific verb ('Get') and an exact resource: one country's public sovereign-credibility reading, followed by a detailed list of included fields. The singular 'one country' clearly separates it from list_countries, and the 'reading' focus separates it from get_latest_briefing.
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?
Clearly describes the context: use it when you want a single country's sovereign-credibility reading with specific metrics. It does not explicitly say 'use get_latest_briefing for briefings' or 'use list_countries to enumerate countries,' but the one-country framing and the list of returned fields provide clear usage context without exclusions.
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.