Skip to main content
Glama

China Lpr

china_lpr
Read-onlyIdempotent

China's PBOC Loan Prime Rate (贷款市场报价利率, LPR) history, the 1-year and 5-year benchmark lending rates, each with its official reference/announcement date. Published monthly on the 20th (or next business day) by the National Interbank Funding Center under PBOC authorization. The 1-year rate anchors most corporate and consumer loans; the 5-year rate anchors mortgages. Returns up to the last 12 monthly announcements (the publisher exposes only a rolling ~1-year window) plus a latest field for the most recent print. Answers "what is the current PBOC LPR", "China's 1-year and 5-year loan prime rate history", "when did the PBOC last cut the LPR". Keyless, sourced live from the National Interbank Funding Center, under PBOC authorization.

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": {
      "months": 12
    },
    "name": "china_lpr"
  }
}

Input Schema

NameRequiredDescriptionDefault
monthsNoHow many of the most recent monthly rows to return, 1-12 (default 12). The upstream only exposes a rolling ~1-year window, so values above 12 are capped at 12.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already cover readOnly/idempotent/non-destructive, but the description adds genuinely new behavior: monthly publication on the 20th (or next business day) by the National Interbank Funding Center under PBOC authorization, keyless access, and a ~1-year rolling cap upstream. It omits latency and rate-limit behavior, so 4 rather than 5.

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 what the tool returns, then cadence, then the return shape, then source/auth. It is dense but every sentence carries information; the rolling ~1-year window is stated twice (once in the return description, once in the schema), which is minor waste.

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?

No output schema exists, and the description compensates by specifying the returned shape: up to 12 monthly rows with rates and reference dates plus a `latest` field. For a single optional-parameter read tool, nothing an agent needs 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% and the single `months` parameter is fully documented with its 1-12 range and cap. The description restates the rolling-window constraint but adds no new semantics about the parameter (e.g., how partial months or the default interact with `latest`), so 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?

Names a specific verb+resource: PBOC LPR history for the 1-year and 5-year benchmark rates with announcement dates. It also implicitly separates itself from the sibling china_lpr_latest by framing itself as history plus a `latest` field, so an agent can tell the two apart.

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?

Concrete example questions ('what is the current PBOC LPR', 'when did the PBOC last cut the LPR') anchor when to reach for this tool, and the 12-month window implies that finer-grained current-value lookups may belong elsewhere. No explicit when-not conditions or named alternative are given, so it stops short of a 5.

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.