Skip to main content
Glama

Get Governance Indicators

get_governance_indicators
Read-onlyIdempotent

World Bank, Worldwide Governance Indicators (WGI), six governance-quality dimensions for ANY country: Voice and Accountability, Political Stability and Absence of Violence/Terrorism, Government Effectiveness, Regulatory Quality, Rule of Law, and Control of Corruption. PREFER for "how corrupt is ", "rule of law in ", "political stability of ", "government effectiveness ", "governance quality ", or as country-risk context alongside news-event data. Pass one ISO country code; returns the latest year available plus the prior year for trend, for all six dimensions, each as a governance estimate (-2.5 weakest to +2.5 strongest) and a percentile-style score (0-100, higher = stronger governance relative to other countries that year).

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_code": "BR"
    },
    "name": "get_governance_indicators"
  }
}

Input Schema

NameRequiredDescriptionDefault
country_codeYesISO country code (e.g., "US", "GBR", "CN").

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive) and open-world scope, so the bar is lower and the description clears it comfortably. It adds genuinely non-obvious behavior: the response covers the latest available year plus the prior year for trend, always across all six dimensions, with the exact value scales (-2.5 to +2.5 estimate and 0-100 percentile-style score).

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?

Front-loaded with source and dimension list, then usage triggers, then return format — a sensible ordering with no filler sentences. The six-dimension enumeration and four example phrasings add length, but each item is functionally load-bearing for disambiguation.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, and the description compensates by specifying the returned dimensions, the two-year span, and both value scales with directionality. For a one-parameter read tool this leaves nothing an agent needs missing.

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 coverage is 100% and the single parameter is already documented with examples, so the schema does the heavy lifting. 'Pass one ISO country code' reinforces the single-country constraint but adds little format or error-handling detail beyond what the schema states.

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 names a specific source (World Bank WGI) and resource (six governance-quality dimensions) and enumerates them explicitly, so it is immediately distinguishable from the numeric siblings get_gdp and get_population. An agent knows exactly what data comes back 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.

Usage Guidelines5/5

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

It gives explicit preferred-trigger phrasings ("how corrupt is <country>", "rule of law in <country>", "political stability of <country>", "governance quality <country>") and a secondary use case as country-risk context alongside news-event data. The 'PREFER' framing actively routes the agent rather than merely describing the tool.

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.