Skip to main content
Glama

Fsi Country Score

fsi_country_score
Read-onlyIdempotent

Fragile States Index score and rank for ONE country, a country-fragility risk measure (12 cohesion/economic/political/social indicators rolled into one 0-120 score; higher = more fragile). Published annually by The Fund for Peace. PREFER for "how fragile is ", " fragile states index", "state fragility risk for ", or as background context on a country before/alongside news-event data (complements gdelt). Pass a country name (e.g. "Somalia", "Brazil", "United States", common aliases like "USA"/"DRC"/"Ivory Coast" are accepted).

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "country": "Somalia"
    },
    "name": "fsi_country_score"
  }
}

Input Schema

NameRequiredDescriptionDefault
countryYesCountry name (e.g. "Yemen", "Germany", "USA").

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and openWorld, so the safety profile is covered. The description adds genuinely useful context beyond that: the annual publication cadence (implying data freshness limits), the scoring direction, and the data source, all of which affect how an agent should interpret and cite results.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One dense but front-loaded block: scope first, then definition, then usage triggers. The definitional parenthetical is long but each clause carries information the agent needs; slightly tighter phrasing could trim redundancy between 'Fragile States Index score' and the restated measure.

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?

With no output schema, the description carries the burden of explaining return values and does so: it names both score and rank and gives the scale. For a one-parameter lookup tool that is sufficient; only explicit null/not-found behavior is unaddressed.

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?

Schema coverage is 100% for the single country parameter, so the baseline would be 3. The description goes beyond the schema by enumerating accepted alias forms ('USA', 'DRC', 'Ivory Coast'), which is real input-format guidance the schema does not provide.

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?

States a specific verb-and-resource ('Fragile States Index score and rank') and immediately constrains scope to 'ONE country', which distinguishes it from the sibling fsi_ranking. The parenthetical also defines the measure itself – 0-120 scale, higher = more fragile, 12 indicators, published by The Fund for Peace – so an agent knows exactly what the number means.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives explicit trigger phrasings ('how fragile is <country>', 'state fragility risk for <country>') and a secondary use case as background context alongside news-event data. It does not explicitly name fsi_ranking as the alternative for multi-country ranking queries, so the exclusion is implied by 'ONE country' rather than stated.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.