Skip to main content
Glama
icen-ai
by icen-ai

China NBS Census Data

ext_cn_census
Read-onlyIdempotent

Query China's population, economic, and agricultural census data via NBS official API. Search by type and keyword, with configurable page size.

Instructions

查询国家统计局普查数据(人口普查、经济普查、农业普查)。通过 NBS 官方 API 获取真实数据。

Args:

  • type (string): 普查类型 "population"(人口)| "economic"(经济)| "agriculture"(农业)

  • keyword (string): 自定义搜索关键词(可选,覆盖默认)

  • pageSize (number): 返回结果数,默认 20

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeNo普查类型population
keywordNo自定义搜索关键词
pageSizeNo返回结果数
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true, openWorldHint=true. Description adds '通过 NBS 官方 API 获取真实数据' confirming read-only nature, but no additional behavioral traits like rate limits or data freshness. No contradiction with annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Concise: one sentence for purpose, then parameter list. Every sentence adds value, front-loaded with purpose. No unnecessary words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Covers purpose and all parameters adequately. Lacks description of output format or return structure, but openWorldHint suggests completeness not required. For a data retrieval tool, a note on expected output would improve completeness, but not essential.

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 coverage is 100%, with descriptions in Chinese that match the parameter list in the description. Description adds minor context: for keyword it says '覆盖默认' (overrides default), for pageSize it states default 20. Baseline 3 is appropriate as schema does most of the work.

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 it queries China NBS census data (population, economic, agriculture) via official API. Clear verb '查询' and resource '普查数据', distinguishing it from sibling tools like ext_fred or cnbs_search that handle other data sources.

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

Usage Guidelines3/5

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

No explicit guidance on when to use this tool versus alternatives. Implied by name and description that it is for Chinese census data, but no when-not-to-use or comparison with similar tools like cnbs_search.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/icen-ai/mcp-cnbs'

If you have feedback or need assistance with the MCP directory API, please join our Discord server