CNBS MCP Server

World Bank Multi-Indicator Query

ext_world_bank_multi

Read-onlyIdempotent

Query multiple World Bank indicators for cross-country comparison. Specify indicators, countries (ISO3), and year range to retrieve economic data such as GDP growth, CPI, and unemployment across nations.

Instructions

同时查询世界银行多个指标，跨国对比。

Args:

indicators (string[]): 指标数组，如 ["GDP_GROWTH","CPI","UNEMPLOYMENT"]
countries (string[]): ISO3 代码数组，如 ["CHN","USA","DEU"]
startYear (number): 起始年份
endYear (number): 结束年份

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": {
      "indicators": "<indicators>"
    },
    "name": "ext_world_bank_multi"
  }
}

Input Schema

Name	Required	Description
`indicators`	Yes	指标数组
`countries`	No	ISO3 代码数组
`startYear`	No	起始年份
`endYear`	No	结束年份

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.1.0Apr 25, 2026

TDQS

A4/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true, openWorldHint=true, indicating a safe read operation. The description adds no behavioral traits beyond that, such as rate limits or error behavior. It does not contradict annotations, so baseline of 3 is appropriate.

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 description is concise: a one-line Chinese summary followed by a structured docstring listing parameters. It is front-loaded and avoids unnecessary detail. The docstring format is slightly redundant with the schema but still efficient.

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?

Given the moderate complexity (multi-indicator, multi-country), the description covers query intent and parameter semantics well. However, it lacks information about the return format (since no output schema exists) and any limitations or pagination. It is adequate but could be more complete.

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 description coverage is 100%, so baseline is 3. The description adds value by providing realistic examples for indicators (e.g., 'GDP_GROWTH', 'CPI') and countries (e.g., 'CHN', 'USA'), and clarifying that countries use ISO3 codes. This practical guidance raises the score to 4.

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 clearly states the tool queries multiple World Bank indicators simultaneously and enables cross-country comparison. The verb 'query' and resource 'multiple World Bank indicators' are specific, and it distinguishes from siblings like ext_world_bank (single indicator) and ext_world_bank_indicators (list indicators).

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 description implies when to use (multi-indicator, cross-country queries) via the title and summary, and provides detailed argument examples. However, it does not explicitly state when not to use or mention alternatives like ext_world_bank for single indicators, which would improve guidance.

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