Skip to main content
Glama

China Lpr Latest

china_lpr_latest
Read-onlyIdempotent

China's most recent PBOC Loan Prime Rate (贷款市场报价利率一年期/五年期, LPR 1Y/5Y) print only, a cheap single-row call for just the current 1-year and 5-year rates and their official reference/announcement date, without the 12-month history. Use china_lpr instead if you need the trend over time. 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": {},
    "name": "china_lpr_latest"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive), and the description adds real context on top: keyless auth, live sourcing from the National Interbank Funding Center under PBOC authorization, and a single-row payload size. It also discloses what is deliberately omitted (the 12-month history), which is the main failure mode an agent could hit.

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?

Two sentences, front-loaded with the scope constraint before the sibling routing. Slightly over-packed with near-synonyms ("most recent print only," "just the current"), but no sentence is wasted.

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 zero-parameter read tool with no output schema, the description covers what is returned, what is excluded, freshness, provenance, and cost profile. There is no ambiguity an agent would need to resolve before calling it.

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?

Zero parameters, so the baseline is 4; there is nothing for the description to disambiguate. It does usefully preview the returned fields (1Y/5Y rates plus reference/announcement date), though that is return-shape information rather than parameter semantics.

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 (PBOC Loan Prime Rate, 1Y/5Y) with an explicit scope limiter ("most recent print only") and even glosses the Chinese term. An agent can distinguish it from china_lpr without opening either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly names the alternative and the condition that selects it: "Use china_lpr instead if you need the trend over time." It also frames the negative case ("without the 12-month history") and positions this as the cheap single-row option.

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.