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

Search CNBS Data

cnbs_search
Read-onlyIdempotent

Search China National Bureau of Statistics indicators and datasets by keyword. Returns dataset ID, name, and time range. Filter by categories and time period, sort by relevance or time.

Instructions

通过关键词搜索中国国家统计局指标和数据(推荐优先使用)。返回匹配的数据集列表,包含 setId、名称、时间范围等信息。

Args:

  • keyword (string): 搜索关键词,如 "GDP"、"CPI"、"人口"

  • pageNum (number): 页码,默认1

  • pageSize (number): 每页数量,默认10

  • sortBy (string): 排序方式,可选 relevance(相关性)或 time(时间)

  • sortOrder (string): 排序顺序,可选 desc(降序)或 asc(升序)

  • categories (string[]): 数据类型过滤,如 ["月度数据", "季度数据"]

  • periodRange (object): 时间范围过滤

Returns: 匹配的数据集列表,包含 setId、名称、时间范围等信息

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
keywordYes搜索关键词,如 "GDP"、"CPI"、"人口"
pageNumNo页码,默认1
pageSizeNo每页数量,默认10
sortByNo排序方式,可选 relevance(相关性)或 time(时间)relevance
sortOrderNo排序顺序,可选 desc(降序)或 asc(升序)desc
categoriesNo数据类型过滤,如 ["月度数据", "季度数据"]
periodRangeNo时间范围过滤
Behavior3/5

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

Annotations (readOnlyHint=true, destructiveHint=false, idempotentHint=true) already inform safe read-only behavior. The description adds return structure details but no extra behavioral disclosures like pagination limits or rate constraints. 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.

Conciseness4/5

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

The description is well-structured with an intro, Args list, and Returns. It is front-loaded with the search purpose. The Args section is slightly redundant with the schema, but overall concise for 7 parameters.

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?

Given 7 parameters, a nested object, and no output schema, the description covers essential aspects: tool function, parameter purposes (both in text and schema), and return format. Lacks search behavior specifics (e.g., fuzzy matching) but sufficient for a search tool.

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%, so the baseline is 3. The description lists parameters with their meanings, largely repeating schema descriptions. It adds minor value by organizing and emphasizing 'keyword' as required, but does not significantly enhance understanding beyond schema.

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?

The description clearly states it searches CNBS data by keyword, returns dataset list with setId, name, time range. It includes '推荐优先使用' (recommended priority use), distinguishing it from siblings like cnbs_search_in_source and cnbs_batch_search.

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?

The description recommends this tool as the primary search ('推荐优先使用'), giving clear context. However, it does not explicitly mention when not to use it or name alternative tools like cnbs_search_in_source or cnbs_batch_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