Skip to main content
Glama

TokenBel Financial Data

entity_news_list

Read-onlyIdempotent

List full published news events across a company's or issuer's full entity graph (the company, its security_issuers, their bonds/shares, and emissions under the company). Accepts a company OR issuer TokenBel id; resolves the entity and returns enriched news events with aggregated links and tags. Supports filtering by event_types, impact_types, and a date_from/date_to range, plus cursor-based pagination.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
uuidYesTokenBel 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. Company or issuer id, usually discovered via search_by_name.
limitNoMax results per page (default 20, max 50).
date_toNoOptional inclusive upper bound on the event date (ISO YYYY-MM-DD).
date_fromNoOptional inclusive lower bound on the event date (ISO YYYY-MM-DD).
event_typesNoOptional filter on news_event.event_type. Valid values: company_news, share_event, bond_event, token_event, emission_event, corporate_action, payment_event, default_risk, financial_report, regulatory_update, tax_update, market_infrastructure, deposit_event, precious_metal_event, currency_market_event, market_data, other. Case-insensitive.
impact_typesNoOptional filter on news_event.impact_type. Valid values: positive, neutral, negative, mixed. Case-insensitive.
cursor_event_idNoOpaque pagination cursor part 1 (the last event id) from the next_cursor returned by a prior call; pass both cursor parts together.
cursor_published_atNoOpaque pagination cursor part 2 (the last event sort-key timestamp) from the next_cursor returned by a prior call; pass both cursor parts together.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
countYes
limitYes
eventsYes
filtersYes
issuer_nameYes
issuer_uuidYes
next_cursorYes
company_nameYes
company_uuidYesTokenBel 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.
requested_uuidYesTokenBel 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.
requested_entity_typeYes

TDQS

A4.5/5.0
Behavior5/5

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

Annotations confirm readOnlyHint and idempotentHint, and the description adds value by detailing that it resolves entities and returns enriched events with aggregated links/tags. 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?

Three sentences: purpose, resolution/return, and filtering/pagination. Front-loaded and efficient with no redundant 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 an output schema exists, the description covers all essential aspects: input, entity graph scope, filters, pagination. It is complete for an 8-parameter tool with good annotations.

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 description coverage is 100%, so baseline 3 applies. The description adds overall context (entity graph resolution) but doesn't significantly enhance individual parameter semantics beyond what the schema already provides.

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 lists full published news events across an entity graph (company, its security_issuers, bonds, shares, emissions). It distinguishes from siblings like bond_list or share_list by focusing on news events and entity resolution.

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 explains when to use this tool (to get news for a company/issuer) and mentions filtering capabilities, but doesn't explicitly state when not to use it or list alternative tools. The context is clear enough for correct selection.

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

Try in Browser

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