Skip to main content
Glama
kevynf

AKBridge MCP Server

by kevynf

option_current_day_szse

Read-onlyIdempotent

Retrieve current-day option contract quotations from Shenzhen Stock Exchange, covering all active contracts with detailed market data for the trading session.

Instructions

深圳证券交易所-期权子网-行情数据-当日合约 https://www.sse.org.cn/option/quotation/contract/daycontract/index.html :return: 深圳期权当日合约 :rtype: pandas.DataFrame

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior2/5

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

The annotations already indicate readOnly, non-destructive, idempotent, and openWorld attributes. The description adds only the return type (pandas.DataFrame) and a URL, but no additional behavioral nuances such as data freshness, pagination, or specific columns. It does not contradict the annotations but adds minimal value beyond them.

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 brief, consisting of a Chinese title, a URL, and a return type. It is front-loaded and efficient, with no unnecessary words. However, the URL is potentially misleading and could be omitted or corrected, but overall the structure is compact.

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 tool has no parameters and no output schema, the description should provide more detail about the returned DataFrame's columns or content. It only says '当日合约' (current day contracts) without specifics. The URL inconsistency further undermines completeness, leaving an agent unsure what data to expect.

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 has 0 parameters, so the schema already fully describes the interface. With no parameters, the description has nothing to explain, and a baseline score of 4 is appropriate since there is no need for compensation.

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 it returns '深圳期权当日合约' (Shenzhen options current day contracts) as a pandas DataFrame, and provides a source URL. However, the URL points to sse.org.cn (Shanghai Stock Exchange), which contradicts the tool name 'szse' and the title '深圳证券交易所', creating confusion about the actual data source.

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?

The description provides no guidance on when to use this tool versus alternatives such as option_current_day_sse or other option data tools. It only states what it returns without any contextual use cases, exclusions, or recommendations.

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