a-stock-mcp

Margin Analysis

margin_analysis

Analyze A-share margin trading: retrieve market-wide summaries or per-stock details for the latest 30 trading days, choosing daily or monthly granularity.

Instructions

融资融券分析：市场汇总或个股明细。

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "margin_analysis"
  }
}

Input Schema

Name	Required	Description	Default
`code`	No	股票代码（6位），如 "600519"。不传则返回全市场汇总。
`period`	No	时间粒度，"monthly"（月度）或 "daily"（每日）。目前统一返回近30个交易日数据。	monthly

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.1Sep 7, 2026

TDQS

A3.5/5.0

Behavior2/5

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

No annotations are present, so the description must carry the full behavioral burden. It only says 'analysis' and indicates the output scope; it does not state read-only behavior, data coverage, how period actually behaves, or any other operational constraints. The word '分析' weakly implies a non-mutating lookup, but that is not sufficient disclosure.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single, well-structured sentence front-loads the tool domain and then states the two output scopes. There is no redundant wording, and every part contributes to understanding the tool.

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?

The tool is simple, has an output schema, and the schema covers parameter semantics, so a long description is not necessary. Yet without annotations and with only a one-line description, the definition lacks behavioral context and alternative-selection guidance, making it minimally complete rather than fully self-sufficient.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema already documents both parameters with defaults, null handling, allowed values, and the 30-trading-day caveat, giving 100% schema description coverage. The description adds only the high-level market-vs-individual distinction that maps to the code parameter, so it provides no significant extra parameter meaning. Baseline 3 is appropriate.

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

Purpose5/5

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

The description names the exact domain (融资融券/margin trading) and the action (analysis), and explicitly scopes output to either market summary or individual stock detail. This clearly differentiates it from the sibling tools such as sector_analyzer or north_flow_tracker, which cover different resources.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The two usage modes are clearly conveyed—market summary vs. individual stock detail—and the schema reinforces that omitting code returns the market-level result. However, there is no explicit guidance about when to select this tool over alternatives or when not to use it, so the choice is only implied by the domain.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server