Skip to main content
Glama
longbridge

longbridge

Official

A/H Premium

ah_premium
Read-onlyIdempotent

Get historical A/H share premium K-line data for a given security symbol, with optional period and count parameters.

Instructions

Get A/H share premium historical K-line data

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
symbolYesSecurity symbol, e.g. "700.HK"
periodNoK-line period: "1m", "5m", "15m", "30m", "60m", "day" (default), "week", "month", "year"
countNoNumber of K-lines to return (default: 100)
Behavior3/5

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

Annotations already provide readOnlyHint, idempotentHint, openWorldHint. The description adds no new behavioral traits beyond stating it 'Get's data. No mention of authentication, rate limits, or response format.

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?

A single sentence that directly states the purpose. No unnecessary words, front-loaded key information.

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?

For a simple data retrieval tool with full schema and annotation coverage, the description is sufficient. Could mention that it deals with A/H premium cross-market data, but not essential.

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?

Schema coverage is 100% with all parameters described (symbol format, period options, count). The description adds no additional meaning beyond the schema, so baseline 3 is appropriate.

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?

Description clearly states the tool retrieves 'A/H share premium historical K-line data', using a specific verb and resource. This distinguishes it from sibling 'ah_premium_intraday' which likely provides intraday data.

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?

No explicit guidance on when to use this tool vs alternatives. The name and sibling list imply it's for historical K-line data, but there is no mention of when not to use it or comparisons to other candlestick-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/longbridge/longbridge-mcp'

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