Skip to main content
Glama
kevynf

AKBridge MCP Server

by kevynf

option_sse_spot_price_sina

Read-onlyIdempotent

Fetch real-time SSE option spot prices and volume data from Sina Finance using an option symbol. Provides structured DataFrame output for financial analysis.

Instructions

新浪财经-期权-期权实时数据 :param symbol: 期权代码 :type symbol: str :return: 期权量价数据 :rtype: pandas.DataFrame

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
symbolNo10003720
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false. The description adds that the return is a pandas DataFrame of volume-price data, but does not disclose any caveats such as data delays, symbol validity, or error behavior.

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?

The description is compact and each line adds information (summary, parameter, return type), though it is presented as a docstring rather than a polished prose description.

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

Completeness2/5

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

Given the lack of an output schema and the many sibling option tools, the description should have specified the SSE scope and the exact data fields returned. It currently only says 'option volume-price data,' which is ambiguous.

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 description explains that 'symbol' is the option code and is a string, which is meaningful given the schema has no per-property description. However, it does not provide format examples or how to obtain valid codes.

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

Purpose3/5

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

The description states 'Sina Finance - Options - Real-time data' and indicates the return is 'option volume-price data', but it does not specify that this is for SSE options or that it returns spot prices, making it hard to distinguish from sibling tools like option_sse_greeks_sina or option_sse_minute_sina.

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 or alternative guidance is provided. The description only includes a docstring with parameter and return types, with no contextual instructions for when to select this tool over others.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/kevynf/akbridge'

If you have feedback or need assistance with the MCP directory API, please join our Discord server