AgentLadle MCP AKShare

get_option_quote

Read-onlyIdempotent

Retrieve option quotes from SSE and SZSE exchanges. Leave exchange empty for all options.

Instructions

Get option quote (SSE, SZSE).

Leave exchange empty for all options. get_option_quote(exchange="SSE")

Args: exchange: SSE/SZSE (optional)

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": "get_option_quote"
  }
}

Input Schema

Name	Required	Description	Default
`exchange`	No

Output Schema

Name	Required	Description	Default
`data`	No
`hint`	No
`error`	No
`cached`	No
`source`	No
`status`	Yes
`updated_at`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 8, 2026

TDQS

A3.5/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, openWorldHint, and idempotentHint. The description adds minimal behavioral context beyond specifying the exchanges (SSE/SZSE). No contradictions with annotations.

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?

The description is extremely concise with two short sentences plus a strategy and example. Every part is front-loaded and useful with no wasted words.

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?

Given the presence of an output schema, the description does not need to explain return values. It covers the basic purpose and parameter usage but could be more complete by mentioning if the quote is real-time or the specific exchange details.

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 schema has 0% description coverage. The description adds meaning by explaining the exchange parameter is optional and providing valid values (SSE/SZSE) via the example and strategy. It could be more explicit about the parameter's purpose.

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 clearly states the tool gets option quotes for SSE and SZSE exchanges. The name and context distinguish it from sibling quote tools like get_quote and get_futures_quote, though it does not explicitly differentiate itself.

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 includes a strategy ('Leave exchange empty for all options') and an example, providing basic guidance on when to use the exchange parameter. However, it does not compare to sibling tools or specify when this tool should be preferred over alternatives.

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

Deploy Server