Skip to main content
Glama
Sign In

Fragile States Index

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Fsi Ranking

fsi_ranking
Read-onlyIdempotent

Rank countries by Fragile States Index score — the N most fragile or N most stable countries in one call, with rank and score. PREFER for "most fragile countries", "most stable/least fragile countries", "top 10 failed states", "which countries are at highest state-fragility risk". direction defaults to "most_fragile".

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": {
      "limit": 5
    },
    "name": "fsi_ranking"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoHow many countries to return (default 10, max 50).
directionNoWhich end of the ranking to return. Default "most_fragile".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds value beyond that by disclosing the return shape ('with rank and score'), that both ends of the ranking come from one call, and that direction defaults to 'most_fragile' — though it omits tie-handling or ranking-year semantics.

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?

Two sentences: the capability and return shape first, then the trigger phrases and default. Every clause carries information an agent needs for selection; nothing is repeated from the schema except the default, which is worth reinforcing.

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 annotations covering safety and a fully specified two-parameter schema, the remaining burden is small and the description covers output content and defaults. Minor gap: it doesn't clarify which FSI edition/year or how ties are broken, but no output schema exists so higher detail isn't strictly required.

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% and both parameters (limit, direction with its enum) are fully documented in the schema, including the max of 50. The description only restates the default direction, so baseline 3 applies.

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 — 'Rank countries by Fragile States Index score' — and immediately bounds the scope to the N most fragile or N most stable, with rank and score returned. An agent can distinguish it from fsi_country_score (single-country lookup) without opening either schema.

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?

The 'PREFER for ...' line gives four concrete phrasings that select this tool, which is strong routing guidance. It does not name an alternative tool or state when not to use it, so it stops short of full when/when-not coverage.

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

All Fragile States Index toolsInspect
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.

Resources