Skip to main content
Glama
kevynf

AKBridge MCP Server

by kevynf

macro_china_au_report

Read-onlyIdempotent

Fetch the Shanghai Gold Exchange report from 2010-03-31 to present, returning a pandas DataFrame for China gold market analysis.

Instructions

上海黄金交易所报告,数据区间从20100331-至今 https://datacenter.jin10.com/reportType/dc_sge_report :return: pandas.DataFrame

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, so safety/idempotency are covered. The description adds the temporal coverage boundary, which is useful, but says nothing about refresh cadence, pagination, or completeness of the returned report.

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?

Two short lines with the key fact (what report, from when) front-loaded; the source URL is a legitimate reference. The ':return: pandas.DataFrame' token is a docstring artifact, but with no output schema it does convey return type, so little is wasted.

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 parameterless macro pull the description covers source and date range, but it omits what columns/fields the report contains and whether results are a single snapshot or a series. With no output schema, this leaves the return shape under-specified.

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 (empty schema, 0 required), so there is no parameter semantics to explain and the baseline is 4. The stated coverage start date (20100331) is the only input-relevant constraint.

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

Purpose3/5

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

Names a specific resource (上海黄金交易所报告 / SGE report) and its data range, so the agent knows the content domain. But there is no verb, and among many near-neighbour gold/SGE siblings (spot_hist_sge, spot_quotations_sge, spot_golden_benchmark_sge, macro_china_fx_gold) nothing states how this report differs from them.

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 only gives the data coverage window; it never says when to choose this tool over the other SGE/gold macros, nor any usage conditions or prerequisites. The link is a data-source reference, not 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