Skip to main content
Glama
kevynf

AKBridge MCP Server

by kevynf

macro_china_hk_ppi

Read-onlyIdempotent

Retrieves Hong Kong manufacturing Producer Price Index (PPI) year-over-year rates as a structured pandas DataFrame from East Money economic data.

Instructions

东方财富-经济数据一览-中国香港-香港制造业 PPI 年率 https://data.eastmoney.com/cjsj/foreign_8_8.html :return: 香港制造业 PPI 年率 :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 read-only, idempotent, and non-destructive behavior, so the description need not repeat that. The description adds the data source URL and the return type (pandas DataFrame), providing some context beyond the annotations, but it does not detail data granularity, date ranges, or update frequency.

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 very brief and includes essential elements: source, indicator, and return type. It is appropriately sized, though the structure is somewhat fragmented as a title-like fragment rather than a full descriptive sentence.

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?

Given the tool's simplicity (no parameters, no output schema), the description explains the return value as a DataFrame of the HK manufacturing PPI YoY. However, it omits useful details such as the time range, frequency, or columns of the returned data, which could be important for correct interpretation.

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 has zero parameters and an empty input schema, so the baseline for this dimension is 4. The description does not need to clarify parameter semantics, and none are missing.

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 the tool returns Hong Kong Manufacturing PPI year-over-year data from East Money, including a specific source URL and return type. It distinguishes this tool from sibling macro indicators by naming the exact metric and region.

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?

The description provides no guidance on when to use this tool versus alternatives such as other macro_china indicators. It does not mention exclusions, alternatives, or contextual use cases, leaving the agent to infer its applicability.

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