China Macro & Supply Signals

China Macro Revision Monitor

china-macro-revision-monitor

Read-only

Monitor bounded China macro observations and historical revisions from the official World Bank WDI source=2 API. — $0.02/call, x402 (USDC on base).

Input Schema

TableJSON Schema

Name	Required	Description	Default
`endYear`	No	Inclusive last year, not later than the current UTC year.
`startYear`	No	Inclusive first year. Runtime validation enforces 1960 or later and a maximum 10-year window.
`watchName`	No	Stable private baseline scope. Reuse it in scheduled runs to identify new observations and revisions.	china-macro-main
`indicators`	No	Approved World Development Indicators. Arbitrary codes and other World Bank datasets are rejected.

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the tool is known to be safe. The description adds contextual details about the data source (World Bank WDI source=2) and pricing ($0.02/call), which are useful operational insights beyond annotations.

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?

The description is a single, front-loaded sentence with a concise pricing tag. Every word adds value without redundancy.

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?

With no output schema, the description should clarify what the tool returns (e.g., list of observations/revisions), but it only says 'monitor' without specifying the output shape. The schema covers input constraints well, but return semantics are incomplete for an agent deciding whether to invoke it.

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%, so the schema already thoroughly documents all four parameters. The description does not add extra parameter-level meaning, thus meeting the baseline of 3.

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 monitors 'China macro observations and historical revisions' from the World Bank WDI source=2 API, with a specific verb and resource. It distinguishes itself from sibling monitors by focusing on China macro data and revisions.

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 gives clear context that this tool is for China macro data monitoring from WDI, but it does not explicitly mention when to use it over alternatives or list exclusions. It implies usage via the domain-specific focus.

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

All China Macro & Supply Signals tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4/5.0

Disambiguation5/5

Each monitor targets a distinct data domain: 1688 suppliers, OECD FDI, GLEIF LEI entities, and World Bank macro revisions. The pricing_info tool is clearly separate as a billing helper. No two tools overlap in purpose.

Naming Consistency4/5

The four data monitors follow a consistent 'china-<domain>-monitor' pattern, making the tool's purpose predictable. pricing_info deviates but serves a distinct meta-function, so the minor inconsistency is acceptable.

Tool Count5/5

With 5 tools, the bundle is well-scoped for a China macro and supply signals monitor server. Each tool covers a different aspect, and none are redundant or excessive.

Completeness4/5

The surface covers macro data, FDI flows, entity changes, and supplier supply-side metrics. Missing potentially useful monitors (e.g., trade or inflation) but core workflows are well covered with no dead ends.

Resources

Need Help?