Skip to main content
Glama
Sign In
a-share-mcp

a-share-mcp

by shouldnotappearcalm
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get_suspensions

Retrieve suspended A-share stocks for a specified date or the current date. Returns a table of stocks with tradeStatus==0 in markdown, JSON, or CSV format.

Instructions

    List suspended stocks for a date.

    Args:
        date: Optional 'YYYY-MM-DD'. If None, uses current date.
        limit: Max rows to return. Defaults to 250.
        format: Output format: 'markdown' | 'json' | 'csv'. Defaults to 'markdown'.

    Returns:
        Table of stocks where tradeStatus==0.

Input Schema

NameRequiredDescriptionDefault
dateNo
limitNo
formatNomarkdown

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior3/5

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

With no annotations provided, the description carries full burden. It discloses output format options and default behaviors (current date, 250 limit), but lacks details on permissions, rate limits, error handling, or data freshness. It adequately describes core behavior but misses advanced operational context.

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?

Well-structured with clear sections (purpose, args, returns). Every sentence adds value, though the 'Args' and 'Returns' headers are slightly verbose. Efficiently front-loaded with the core purpose first.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no annotations and no output schema, the description provides solid coverage: clear purpose, full parameter semantics, and return format explanation. It lacks sibling differentiation and some behavioral details, but is largely complete for a read-only query tool.

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

Parameters5/5

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

Schema description coverage is 0%, so the description fully compensates by explaining all three parameters: date (optional, format, default logic), limit (purpose, default), and format (options, default). It adds crucial meaning beyond the bare schema, including conditional behavior and enum values.

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 clearly states the specific action ('List suspended stocks') and resource ('stocks'), with precise scope ('for a date'). It distinguishes from siblings by focusing on suspended stocks (tradeStatus==0), unlike other tools that retrieve different financial data types.

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 description implies usage context through 'for a date' and the return condition 'tradeStatus==0', but lacks explicit guidance on when to use this tool versus alternatives like 'get_all_stock' or 'get_stock_basic_info'. No exclusions or prerequisites are mentioned.

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