Skip to main content
Glama

China Rmb Fixing

china_rmb_fixing
Read-onlyIdempotent

China's RMB central parity (人民币汇率中间价), the daily USD/CNY fixing the PBOC publishes at 09:15 Beijing time, for a named date or the latest: USD/CNY by default, or any published pair (EUR/CNY, 100JPY/CNY, HKD/CNY, GBP/CNY and more, or all), with an optional history window. Answers "USD/CNY central parity today", "what was the PBOC fixing on 2026-11-06", "RMB midpoint history". A weekend or holiday date returns found:false with reason no_fixing_for_date and the nearest earlier fixing. Keyless, sourced live from the China Foreign Exchange Trade System.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "date": "2026-11-06",
      "pair": "USD/CNY"
    },
    "name": "china_rmb_fixing"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateNoDate as YYYY-MM-DD (Beijing). Omit for the latest published fixing.
pairNoCurrency pair such as "USD/CNY" (default), "EUR/CNY", "100JPY/CNY", "CNY/KRW", or "all" for every published pair.
history_daysNoAlso return the fixings for this many calendar days up to the date, 0-366 (default 0).

Output Schema

NameRequiredDescriptionDefault
dateNo
hintNo
pairNo
rateNo
foundNo
ratesNo
reasonNo
sourceNo
historyNo
messageNo
data_as_ofNo
is_weekendNo
nearest_earlierNonearest earlier fixing when the requested date had none
quote_conventionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already declare read-only, idempotent, non-destructive and open-world, so the bar is lower; the description still adds real context beyond them: keyless access, live sourcing from CFETS, and the exact weekend/holiday behavior (found:false with reason no_fixing_for_date plus the nearest earlier fixing). That failure-mode disclosure is what an agent needs to interpret a null result.

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 single dense sentence front-loads the resource and time, followed by example queries and edge-case behavior in a logical order. It is long and the pair enumeration plus example questions overlap somewhat, but nearly every clause carries information.

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?

An output schema exists so return values needn't be described, and the description goes further by explaining the found:false path. For a zero-required-parameter lookup with full schema coverage, nothing an agent needs in order to call it correctly is missing.

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 all three parameters including the 0-366 history_days range are already documented. The description restates the default pair and `all` keyword and adds the Beijing-time framing, but contributes no syntax or constraint beyond the schema — the baseline 3 applies.

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 resource and verb: the daily USD/CNY central parity the PBOC publishes at 09:15 Beijing time, with the default pair and the `all` option spelled out. It is clearly distinguishable from the sibling macro tools (china_lpr, china_rates, china_omo), which cover different data.

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?

Usage is conveyed through concrete example questions ("USD/CNY central parity today", "what was the PBOC fixing on 2026-11-06", "RMB midpoint history") plus the rule to omit `date` for the latest fixing. It does not explicitly name an alternative tool or exclusion, but the scope is narrow enough that no routing ambiguity is left.

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.