Skip to main content
Glama
kevynf

AKBridge MCP Server

by kevynf

macro_china_market_margin_sz

Read-onlyIdempotent

Retrieve Shenzhen margin trading and short selling report data from 20100331 to present as a pandas DataFrame.

Instructions

深圳融资融券报告,数据区间从20100331-至今 https://datacenter.jin10.com/reportType/dc_market_margin_sz :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.3/5.0
Behavior3/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, openWorld), so the bar is lower. The description adds genuinely useful behavior context: the data starts at 20100331, the upstream source URL, and that the return is a pandas.DataFrame. It does not mention update frequency or rate limits.

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?

Three short lines with the dataset and coverage front-loaded. The source URL and return-type line are compact and informative rather than padded, though the text is essentially the title expanded with a URL.

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 no-param macro data fetch with safety annotations already present, the description is mostly sufficient, but it never describes what the returned DataFrame contains (e.g. margin balance, buy/sell amounts), which matters for a data-consumer tool with no output schema.

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 0 parameters, so the baseline is 4. There is no parameter meaning to add, and the description correctly does not invent any argument semantics.

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 a specific dataset (Shenzhen margin financing/securities lending report) and its temporal coverage from 20100331 to present, so it is clear what is fetched. It does not explicitly differentiate itself from the sibling macro_china_market_margin_sh, though the Shenzhen location is implied by name and text.

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 when-to-use guidance, no prerequisites, and no mention of the obvious alternative macro_china_market_margin_sh for Shanghai data. The only useful hint is the data-range coverage, which is not usage 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