Skip to main content
Glama
kevynf

AKBridge MCP Server

by kevynf

macro_china_market_margin_sh

Read-onlyIdempotent

Retrieves Shanghai stock market margin trading and short selling data from 2010-03-31 to present as a pandas DataFrame for financial analysis.

Instructions

上海融资融券报告,数据区间从 20100331-至今 https://datacenter.jin10.com/reportType/dc_market_margin_sse :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 declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds genuinely useful context: the historical start date (20100331) and the upstream data source URL. It does not, however, describe the returned columns or data frequency, which matters for a macro dataset.

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?

Very short and front-loaded: the resource and date range come first, followed by a source link and the Sphinx-style ':return: pandas.DataFrame'. The URL and return annotation are mildly useful; nothing is padded.

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 data-fetch tool with no output schema, the description covers the resource, date range and return type, but does not say what fields/metrics the DataFrame contains or its update frequency, which an agent would need to use the result intelligently.

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 per the rubric the baseline is 4. There is nothing further the description could add about parameter meaning.

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 specific resource, '上海融资融券报告' (Shanghai margin trading report), and pins the data coverage to 20100331-present. The '上海' qualifier implicitly separates it from the sibling macro_china_market_margin_sz, though that sibling is never named explicitly.

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?

There is no statement of when to use this tool versus alternatives, no prerequisites, and no mention of the Shenzhen counterpart. Usage must be inferred entirely from the tool name and data-range note.

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