Skip to main content
Glama
kevynf

AKBridge MCP Server

by kevynf

macro_china_real_estate

Read-onlyIdempotent

Fetch China's National Housing Climate Index, a macroeconomic indicator for real estate, returned as a structured DataFrame.

Instructions

国房景气指数 https://data.eastmoney.com/cjsj/hyzs_list_EMM00121987.html :return: 国房景气指数 :rtype: pandas.DataFrame

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=true, and destructiveHint=false, covering the safety profile. The description adds a source URL and return type (pandas.DataFrame) but does not disclose data frequency, coverage, or limitations. It does not contradict the 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 extremely short and free of filler, with the URL and return type being useful additions. However, it repeats '国房景气指数' three times and lacks structured formatting, which slightly detracts from clarity.

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

Completeness3/5

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

For a zero-parameter data retrieval tool with strong annotations, the description is minimally adequate: it names the index and provides a source URL. Yet it omits details on what the index measures, update frequency, and how it differs from other China real estate indicators, so an agent must infer context from the name alone.

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?

The tool accepts zero parameters and the input schema is empty, so there are no parameter semantics to describe. The baseline for zero-parameter tools is 4, and the description contains no irrelevant parameter information.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description identifies the resource as 国房景气指数 (China Housing Prosperity Index) and provides a source URL, but it lacks an explicit verb or action (e.g., 'fetches' or 'retrieves'). It does not differentiate from sibling tools like macro_china_new_house_price, though the name is fairly specific.

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

Usage Guidelines2/5

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

No guidance is given on when to use this tool versus alternative macro China tools. The description provides no context for selection, exclusions, or preferred scenarios, leaving the agent to guess based on the name alone.

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/kevynf/akbridge'

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