Skip to main content
Glama
kevynf

AKBridge MCP Server

by kevynf

macro_china_fx_reserves_yearly

Read-onlyIdempotent

Retrieve China's annual foreign exchange reserves data from 2014 to present as a pandas DataFrame.

Instructions

中国年度外汇储备数据,数据区间从 20140115-至今 https://datacenter.jin10.com/reportType/dc_chinese_fx_reserves :return: 中国年度外汇储备数据 :return: pandas.DataFrame

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint. The description adds the concrete date range and return type ('pandas.DataFrame'), which are useful behavioral details not found in the annotations. It does not contradict any annotation.

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 short and front-loaded with the core dataset name and date range. The repeated ':return:' lines are slightly redundant, but the overall structure is efficient and easy to scan.

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 retrieval tool with no output schema and complete annotation coverage, the description supplies the data range, source URL, and return type. It is nearly complete, though it could mention update frequency or data granularity.

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, so there are no parameter semantics to document. The description correctly does not invent parameter details, and the baseline for 0 params 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?

The description names the exact resource ('中国年度外汇储备数据') and its temporal coverage ('20140115-至今'). It is clearly distinguishable from sibling macro tools such as macro_china_fx_gold or macro_china_foreign_exchange_gold, though it does not explicitly state a verb like 'fetch' or 'retrieve'.

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 gives the data range but no guidance on when to use this tool versus alternatives. It does not mention exclusions, prerequisites, or related sibling tools, leaving usage entirely implicit.

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