TokenBel Financial Data

share_payouts_get

Read-onlyIdempotent

Get dividend/payout history and an aggregate summary for a single share by its TokenBel internal identifier (field name: uuid). Use search_by_ticker to find a share, then call this tool with the returned uuid value. Event period_type is annual/halfyear/quarterly. Event status meanings: declared = payout declared/expected/paid depending on dates, no_dividend = issuer declared no payout, cancelled = revoked. Summary money totals use declared events only. dividend_yield_pct is a nominal-based proxy (latest declared amount / nominal value * 100), not a market-price dividend yield.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`uuid`	Yes	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. Share id, usually discovered via search_by_ticker.

Output Schema

TableJSON Schema

Name	Required	Description
`events`	Yes
`ticker`	Yes
`summary`	Yes
`currency`	Yes
`share_uuid`	Yes	TokenBel internal identifier: opaque hexadecimal string, usually 8 characters such as "78c7e502"; despite uuid field names, it is not an RFC UUID and normally has no hyphens.
`nominal_value`	Yes

TDQS

A4.6/5.0

Behavior5/5

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

Annotations already indicate read-only and idempotent behavior. The description adds valuable context: summary money totals use declared events only, and dividend_yield_pct is a nominal-based proxy, not market-price yield. 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.

Conciseness4/5

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

The description is longer than necessary but well-structured: it starts with the main purpose, then usage hints, then parameter and output details. Every sentence provides useful information, though some details (like status meanings) could be slightly condensed.

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 the presence of an output schema, the description covers key aspects: the identifier, event types, status meanings, and important caveats about the summary and dividend_yield_pct. It also provides a usage workflow. No missing information for this tool's context.

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?

Schema coverage is 100% and the schema description already explains the uuid parameter in detail. The description reinforces that it is the TokenBel internal identifier and how to obtain it, adding value beyond the schema.

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?

The description clearly states it gets dividend/payout history and an aggregate summary for a single share by its unique internal identifier (uuid). It distinguishes from other tools like search_by_ticker by specifying the workflow.

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?

The description provides explicit guidance: first use search_by_ticker to find the share, then call this tool with the returned uuid. It also explains event period_type and status meanings, helping the agent understand when to use each piece of data. However, it does not explicitly list alternative tools or exclusions.

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?