Skip to main content
Glama

Get China liquidity

get_china_liquidity
Read-only

Read the latest Mako-curated PBoC balance-sheet publication (CNY trillions + source URL + as_of_month + note). Public read — suitable for surfacing directly when explaining the China leg of global liquidity. The same value is also embedded in get_financial_conditions.pillars.global_liquidity.components.china and is the PBoC leg of the Money card of get_dashboard; this tool exists for direct/auditable access.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_china_liquidity"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
rowNo
statusNo
terms_glossaryNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / additionalProperties
      Previous value: -falseNew value: +true
  2. First observed

TDQS

A4.4/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 safety profile is covered. The description adds meaningful context beyond that: it is a public read requiring no auth, returns provenance fields (source URL, as_of_month, note), and duplicates data available elsewhere. It does not discuss caching or freshness beyond 'latest'.

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 the core action and payload, then the routing/context sentence. Slightly dense in the second sentence with a long nested path (get_financial_conditions.pillars.global_liquidity.components.china), but every clause earns its place by clarifying duplication and intent.

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?

With a rich output schema and full annotations, the description need not explain return values, and it still names the key fields. It covers sourcing, alternative access paths, and intended use, leaving no gap for a no-parameter read tool.

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?

The tool takes zero parameters, so there is nothing to disambiguate; the baseline of 4 applies. The description correctly implies a no-argument read, and the enumerated return fields are extra value even though they belong to the output 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?

States a specific verb and resource: 'Read the latest Mako-curated PBoC balance-sheet publication,' and enumerates what is returned (CNY trillions, source URL, as_of_month, note). It explicitly distinguishes itself from siblings by noting the value is also embedded in get_financial_conditions and get_dashboard, so an agent knows exactly what this tool uniquely provides.

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?

Tells the agent when to use it ('suitable for surfacing directly when explaining the China leg of global liquidity') and why it exists versus the alternatives ('direct/auditable access' vs. the embedded copies). It does not state an explicit when-not-to-use, but the overlap with get_financial_conditions/get_dashboard is clearly delineated.

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.

Resources