Skip to main content
Glama

China Omo

china_omo
Read-onlyIdempotent

PBOC open market operations for one day (公开市场业务操作): each operation's type (7-day or overnight reverse repo, Hong Kong central bank bill issue), tenor, accepted amount in units of 100 million CNY and rate, parsed from that day's official trading announcement, plus the announcement text. Pass date (YYYY-MM-DD) or omit it for the latest day. A day with no announcement (weekend, holiday, or no operation) returns found:false with reason no_operation_notice and the nearest announcement dates; a day with a zero-volume 7-day reverse repo returns the zero operation explicitly. Answers "today's PBOC reverse repo", "how much liquidity did the PBOC inject on 2026-11-10", "PBOC 7-day reverse repo rate". Keyless, sourced live from the People's Bank of China.

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-10"
    },
    "name": "china_omo"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateNoOperation date as YYYY-MM-DD. Omit for the latest announced day.

Output Schema

NameRequiredDescriptionDefault
dateNo
hintNo
foundNo
reasonNo
sourceNo
messageNo
noticesNo
data_as_ofNo
operationsNo
parse_statusNo
zero_volume_noticeNo
nearest_later_notice_dateNo
nearest_earlier_notice_dateNo
reverse_repo_total_cny_100mNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already establish read-only and idempotent semantics, and the description adds substantial context beyond them: keyless access, live sourcing from the PBOC, and the exact failure behavior (found:false with reason no_operation_notice plus the nearest announcement dates) and the zero-volume edge case. Those edge-case disclosures are the kind of detail an agent needs before deciding whether a null result means failure or no operation.

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 definition is front-loaded with the resource and its payload, then the date rule, then edge cases, then example questions, so each part earns its place. The first sentence is dense and could be split for readability, but nothing is redundant.

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?

For a one-parameter, read-only lookup with an output schema, the description covers everything an agent needs: what it returns, how to scope by date, how to handle no-result days, and example query phrasings. It does not need to restate return values because an output schema exists, and the edge-case behavior is fully covered regardless.

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 coverage is 100% and the single `date` parameter is already documented, so the description only needs to add meaning beyond it; it does so by specifying the format and the default behavior when omitted, and by explaining what a missing date produces. That pushes it slightly above the baseline.

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 (PBOC open market operations for one day) and enumerates the returned fields: operation type, tenor, accepted amount in 100 million CNY, rate, and announcement text. This is precise enough to separate it from rate-fixing or LPR siblings without opening the schema.

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?

Gives explicit invocation guidance (pass `date` as YYYY-MM-DD or omit for the latest day) and lists the concrete questions it answers, such as today's reverse repo and liquidity injection on a given date. It does not explicitly name a sibling tool as the alternative for related PBOC data, but the intended use case is unambiguous.

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.