Skip to main content
Glama

AutoTasker Hub — China Social Data API

worldbank_indicator

World Bank development indicator series for a country (GDP, population, inflation, etc). $0.01 USDC.

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": {
      "country": "<country>",
      "indicator": "<indicator>"
    },
    "name": "worldbank_indicator"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
countryYesCN
indicatorYesNY.GDP.MKTP.CD

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3/5.0
Behavior3/5

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

With no annotations present, the description carries the full behavioral burden. It does disclose the notable trait that this is a paid call costing $0.01 USDC, which is genuinely useful context an agent cannot get from the schema. However, it says nothing about what a call returns, how errors or unknown indicator codes are handled, or whether payment must be pre-arranged.

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?

Two short sentences, no padding, with the resource identified first and the price disclosed second. It is appropriately sized, though the extreme terseness contributes to the missing parameter guidance.

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

Completeness3/5

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

For a simple data-fetch tool with no output schema, the description covers the resource and the cost. It falls short on the parts that actually make the tool hard to invoke correctly: indicator code format, country value format, and what limit controls.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate and it largely does not. The indicator examples (GDP, population, inflation) hint at the 'indicator' parameter's domain but never explain that it expects World Bank code strings like the schema default NY.GDP.MKTP.CD; 'country' and 'limit' are entirely unaddressed.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Names a specific resource (World Bank development indicator series for a country) and disambiguates the domain with parenthetical examples (GDP, population, inflation). It is immediately clear what class of data the tool returns, though the description never uses an explicit verb like 'fetch' or 'retrieve'.

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

Usage Guidelines2/5

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

There is no guidance on when to use this tool versus alternatives, no prerequisites, and no exclusions. The examples of indicator types imply the domain of use but give the agent nothing about when a different tool would be the better choice.

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.