Skip to main content
Glama
kevynf

AKBridge MCP Server

by kevynf

bond_spot_quote

Read-onlyIdempotent

Fetch spot bond market-making quotes from China's interbank bond market, providing bid/ask prices and quote details for market analysis and trading decisions.

Instructions

中国外汇交易中心暨全国银行间同业拆借中心-市场数据-债券市场行情-现券市场做市报价 https://www.chinamoney.com.cn/chinese/mkdatabond/ :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 description includes the source URL and return type, which offers some context about data origin, but it does not disclose any behavioral traits like data freshness, pagination, or potential network dependencies. The annotations already declare read-only and non-destructive behavior, so the description adds little beyond that.

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 very short and contains only a source URL and return type, which is efficient but lacks structural prose. It is not bloated, though it is under-specified in other dimensions.

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?

No output schema exists, so the description should clarify what the returned DataFrame contains. It merely repeats '现券市场做市报价' (spot market-making quotes), which adds little beyond the tool name, leaving the row/column structure and data scope unclear.

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 takes no parameters, and the input schema is empty with 100% coverage. The description does not need to explain parameter semantics, so the baseline of 4 applies.

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 identifies the tool as providing spot market-making quotes from China Money, but it does so in a fragmentary way with no explicit verb. It restates the tool name with minimal elaboration, making it hard to distinguish from sibling bond spot tools without deeper inspection.

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 guidance is provided on when to use this tool versus similar bond quote tools. There are no exclusions, alternatives, or context cues beyond the source URL.

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