TokenBel Financial Data

bond_list

Read-onlyIdempotent

List active BCSE exchange-listed bonds with optional filtering by securities issuer TokenBel internal id (parameter name: issuer_uuid) and today-trading flag. Use issuer_uuid from search_by_name results where entity_type="issuer". Supports cursor-based pagination.

Input Schema

TableJSON Schema

Name	Required	Description
`limit`	No	Max results (1-1000, default 50)
`is_trading`	No	Filter by is_traded_today flag: true means traded today, not historical liquidity
`cursor_uuid`	No	TokenBel internal identifier: opaque hexadecimal string, usually 8 characters such as "78c7e502"; despite uuid field/tool names, it is not an RFC UUID and normally has no hyphens. Pagination cursor id from next_cursor before the \| delimiter.
`issuer_uuid`	No	TokenBel internal identifier: opaque hexadecimal string, usually 8 characters such as "78c7e502"; despite uuid field/tool names, it is not an RFC UUID and normally has no hyphens. Filter by security_issuer id from search_by_name result with entity_type="issuer".
`cursor_created_at`	No	Pagination cursor datetime (ISO 8601)

Output Schema

TableJSON Schema

Name	Required	Description	Default
`bonds`	Yes
`count`	Yes
`next_cursor`	Yes

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnlyHint and idempotentHint. Description adds behavioral details: lists only active bonds, BCSE exchange, today-trading flag meaning, and cursor pagination. No contradictions.

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?

Two sentences: first explains purpose and filters, second adds pagination and cross-tool guidance. No fluff, front-loaded key information.

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

Completeness5/5

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

Given output schema exists and annotations are complete, the description covers purpose, filtering, pagination, and dependency. No gaps identified.

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%, so baseline 3. Description adds value for issuer_uuid (source from search_by_name) and clarifies is_trading meaning. Other parameters are well-described in schema already.

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?

States specific verb 'list', resource 'active BCSE exchange-listed bonds', and mentions optional filters (issuer_uuid, is_trading). Clearly distinguishes from siblings like bond_get_by_uuid or other list tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides guidance on using issuer_uuid from search_by_name results and mentions pagination. Does not explicitly contrast with alternatives like bond_get_by_uuid, but the context is clear.

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

All TokenBel Financial Data tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.4/5.0

Disambiguation5/5

Each tool targets a distinct entity or operation: bonds, shares, tokens, companies, issuers, currency rates, news, and searches. No two tools have overlapping purposes; even similar tools like bond_list and company_bonds_list are clearly differentiated by scope (global vs per-company).

Naming Consistency4/5

Tools mostly follow a pattern of entity_noun + verb (e.g., bond_list, share_get_by_uuid, company_bonds_list). Some exceptions like currency_rate_get and entity_news_list place the verb at the end, but the pattern is predictable and readable.

Tool Count5/5

With 19 tools covering bonds, shares, tokens, companies, issuers, currency rates, news, and trading statistics, the number is well-calibrated to the domain. Each tool serves a clear purpose without redundancy.

Completeness5/5

The tool surface provides comprehensive read access to the financial data domain: search, retrieval, listing with filters, trading statistics, and news. All expected query operations are present, and no obvious gaps are apparent for a data provider.

Resources

Need Help?