Skip to main content
Glama

China House Prices

china_house_prices
Read-onlyIdempotent

China's NBS 70-city residential price indexes, new-build commercial housing (新建商品住宅) and resale/existing housing (二手住宅), year-on-year and month-on-month, for Beijing, Shanghai, Shenzhen, and 67 other NBS-tracked cities. Pass city (English name, e.g. "Beijing") for that city's history (up to 24 months); pass month ("YYYY-MM") to pin a specific release; pass neither for the latest month's full 70-city cross-section. Index values use the prior period = 100 convention (e.g. 97.7 = a 2.3% year-on-year fall). Answers "Beijing home price index", "which Chinese cities have falling house prices", "China 70-city house price index for August". Keyless, sourced live from the National Bureau of Statistics of China, via Eastmoney's data centre.

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": {
      "city": "Beijing"
    },
    "name": "china_house_prices"
  }
}

Input Schema

NameRequiredDescriptionDefault
cityNoOne of the 70 NBS-tracked cities, by English name (e.g. "Shanghai", "Chengdu"). Omit for all 70 cities in the latest month.
monthNoA specific release month as "YYYY-MM" (e.g. "2026-08"). Omit for the latest available month.

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 declare readOnly/idempotent/non-destructive/openWorld, so the description rightly spends its space on non-obvious behavior: keyless access, live sourcing from NBS via Eastmoney's data centre, a 24-month history cap for a single city, and the prior-period=100 index convention with a worked example (97.7 = -2.3% YoY). That unit convention is the single most important behavioral fact and is not derivable from schema or annotations.

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 series is, then the three parameter modes, then the index convention, then example queries -- a sensible order with no filler sentences. It is dense and runs as one block without line breaks, which costs a little scannability, but 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?

For a two-optional-parameter read tool with no output schema, the definition covers sourcing, coverage limits, units, and return shape (single-city history vs 70-city cross-section) -- everything an agent needs to call it correctly and interpret the numbers. Nothing material is left to inference.

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%, so the baseline is 3, but the description adds two facts the schema omits: that `city` history is capped at 24 months, and that omitting both parameters yields a full 70-city cross-section rather than an empty or default city. It also restates the English-name and YYYY-MM formats already in the schema, which is mild redundancy.

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 the exact resource (NBS 70-city residential price indexes), the two sub-series (new-build 新建商品住宅 and resale 二手住宅), the metrics (YoY and MoM), and the geographic scope (Beijing, Shanghai, Shenzhen + 67 others). No sibling tool covers Chinese property prices, and the definition makes the boundary obvious.

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 modes -- pass `city` for one city's history, pass `month` for a pinned release, pass neither for the latest 70-city cross-section -- plus three natural-language query examples that anchor when to reach for it. It stops short of naming an alternative tool or an explicit when-not-to-use condition, so it lands at 4 rather than 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.