Skip to main content
Glama
kevynf

AKBridge MCP Server

by kevynf

macro_china_gdp

Read-onlyIdempotent

Retrieve China's GDP data from East Money. Get historical GDP figures in a structured format for economic analysis and reporting.

Instructions

东方财富-中国国内生产总值 https://data.eastmoney.com/cjsj/gdp.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 and destructiveHint=false, covering the safety profile. The description adds the data source URL and return type, which is some context, but it does not disclose what the DataFrame contains, time range, or frequency. 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.

Conciseness3/5

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

The description is short and structured, but it contains redundancy: the title is repeated verbatim in the :return: line. The URL is useful, but the docstring could be more concise without losing meaning.

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

Completeness2/5

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

This is a data retrieval tool with no output schema, so the description should explain what the returned DataFrame contains. It only says 'China GDP' and 'DataFrame' without specifying frequency, columns, units, or historical coverage. Given the sibling macro_china_gdp_yearly, the description also fails to clarify how this tool differs.

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 0 parameters, so the baseline is 4. The description provides the return type (pandas.DataFrame), which is the only relevant semantic detail. No parameter documentation is needed.

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

Purpose4/5

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

The description clearly identifies the resource (China GDP) and source (East Money), and specifies it returns a pandas DataFrame. It lacks an explicit verb, but the name and title together make the purpose unambiguous. It does not differentiate from the sibling macro_china_gdp_yearly beyond the name.

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 alternatives such as macro_china_gdp_yearly. There is no mention of use cases, prerequisites, or when not to use it.

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