Skip to main content
Glama
kevynf

AKBridge MCP Server

by kevynf

macro_china_fx_reserves_yearly

Read-onlyIdempotent

Fetches yearly China FX reserves data spanning from 2014 to today, delivered as a pandas DataFrame for financial analysis.

Instructions

中国年度外汇储备数据, 数据区间从 20140115-至今 https://datacenter.jin10.com/reportType/dc_chinese_fx_reserves :return: 中国年度外汇储备数据 :return: 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 cover read-only, idempotent, and non-destructive behavior. The description adds a date range (20140115-至今) and a pandas.DataFrame return type, which are useful, but it does not disclose data frequency, column meanings, or update/refresh behavior, leaving partial ambiguity (e.g., '年度' vs. the full date range).

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 compact but repetitive: '中国年度外汇储备数据' appears twice, and the return annotations duplicate the earlier phrase. The URL and return type occupy space, but the structure is a bit loose and not front-loaded; it could be tightened to a single clear 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?

For a zero-parameter, read-only data tool, the description gives the essential data name, date range, source URL, and return type. However, it omits frequency details (despite the '年度' label), column layout, and how it differs from similar FX reserve tools, so it is adequate but not complete.

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 the schema coverage is trivially 100%. The description correctly indicates no inputs are needed and adds value by clarifying the returned data object, so it meets the baseline for no-parameter tools.

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 states it returns China's annual foreign exchange reserves data, including a source URL and return type. It identifies the resource and conveys a data-retrieval purpose, though it does not explicitly differentiate it from sibling tools like macro_china_fx_gold or macro_china_foreign_exchange_gold at the same level.

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 provided on when to use this tool versus related alternatives, nor are any usage conditions or exclusions mentioned. The tool name and data type imply its use, but there is no explicit context for selection among the many macro_china_* siblings.

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