Zovo Country Data

Search indicators

search_indicators

Read-onlyIdempotent

Use this when the user names an economic, social or environmental measure in words and you need its World Development Indicators code before comparing or ranking countries. Common indicators are listed first. Returns up to 15 codes and names. Does not return data values.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "<query>"
    },
    "name": "search_indicators"
  }
}

Input Schema

Name	Required	Description	Default
`query`	Yes	Keyword or short phrase for the measure, e.g. inflation, GDP per capita PPP, CO2 per capita.

Output Schema

Name	Required	Description	Default
`query`	Yes
`source`	Yes
`results`	Yes
`total_matches`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 8, 2026

TDQS

A4.4/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 closed-world behavior, so the bar is lower. The description still adds real context beyond them: a result cap of 15, relevance ordering ('Common indicators are listed first'), and a scope exclusion ('Does not return data values'). The return-shape detail overlaps somewhat with the existing output schema, which keeps it from a 5.

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?

The trigger condition is front-loaded in the first sentence, and the remaining sentences are short and purposeful. The 'Returns up to 15 codes and names' line is mildly redundant given an output schema exists, but it is not wasteful enough to harm readability.

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?

For a one-parameter lookup tool with rich annotations and an output schema, the description covers everything an agent needs: trigger, input form, ordering, result cap, and the fact that no data values come back.

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?

The single query parameter is fully documented in the schema, including example keywords, so the structured baseline already does the work. The description only loosely reinforces this with 'names ... in words', adding no syntax, length, or matching-behavior detail beyond the schema.

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 states a specific verb and resource ('search' for an indicator's 'World Development Indicators code') and clarifies the input form ('names ... in words'). It also distinguishes this from the siblings by positioning the tool as the lookup step that precedes compare_countries and rank_countries.

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?

The trigger is explicit ('Use this when the user names an economic, social or environmental measure in words and you need its ... code before comparing or ranking countries'), which routes the agent here first and to the sibling comparison/ranking tools afterward. The boundary 'Does not return data values' also signals when this tool stops being the right call.

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

All Zovo Country Data tools Inspect

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

Need Help?