Skip to main content
Glama
kevynf

AKBridge MCP Server

by kevynf
Behavior2/5

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

The annotations already declare the tool as read-only, idempotent, and non-destructive. The description adds the return type (pandas DataFrame) but does not disclose additional behavioral traits such as data freshness, rate limits, or pagination behavior. It does not contradict annotations but contributes little 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.

Conciseness3/5

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

The description is short but not optimally structured. It repeats the same Chinese phrase in the main text and in the return field, and includes a long URL that may not be essential. The key information is front-loaded but there is some redundancy.

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?

With zero parameters and no output schema, the description should explain what the returned DataFrame contains. It only states the return type, not the columns or data structure. However, for a simple real-time quote tool, this may be sufficient for basic selection and invocation, but not for full interpretation of the output.

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?

Since there are zero parameters, the schema is trivially fully covered. The baseline for 0-parameter tools is 4, and the description adds no parameter-specific information because none is needed.

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 states '腾讯财经-港股-AH-实时行情' which identifies the tool as providing real-time AH market quotes from Tencent Finance, and the function name 'spot' reinforces this. However, it does not distinguish this tool from sibling tool stock_zh_ah_spot_em, which likely offers similar data from a different 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 select this tool over alternatives. It only includes a URL and a return type; there is no mention of use cases, exclusions, or comparisons with related tools.

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