Skip to main content
Glama
kevynf

AKBridge MCP Server

by kevynf

macro_china_gdp_yearly

Read-onlyIdempotent

Fetch China's yearly GDP growth rate reports from Jin10 Data Center, covering 2011-01-20 to present, for economic trend analysis.

Instructions

金十数据中心-中国 GDP 年率报告,数据区间从 20110120-至今 https://datacenter.jin10.com/reportType/dc_chinese_gdp_yoy :return: 中国 GDP 年率报告 :rtype: pandas.DataFrame

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true and openWorldHint=true, so the safety profile is covered. The description adds useful behavioral context – the historical coverage start date and that the return is a pandas.DataFrame – but nothing about freshness, update cadence, or failure modes.

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?

Front-loaded and short, with the key scope (China GDP yearly, date range) leading. The raw Sphinx-style ':return:'/':rtype:' markers and URL are slightly noisy but not wasteful for a data-fetch tool.

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?

For a parameterless, read-only data retrieval endpoint with full annotation coverage, the description supplies what an agent needs: the resource, the historical range, and the return type. No output schema exists, so the stated DataFrame return is helpful.

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 takes zero parameters, so there is nothing for the description to disambiguate; the baseline for a parameterless tool is 4.

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?

States a specific resource – China GDP yearly rate report from 金十数据中心 – with a source URL. It is distinguishable from quarterly/other-country GDP siblings by the '年率' qualifier, though it does not explicitly name the alternatives it is not.

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?

Provides no when-to-use or when-not-to-use guidance and names no alternative sibling. It only states the data coverage window (20110120 onwards), which is context rather than selection guidance.

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

Deploy Server

Other Tools