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

Name	Required	Description
`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. Company or issuer id, usually discovered via search_by_name.
`limit`	No	Max results per page (default 20, max 50).
`date_to`	No	Optional inclusive upper bound on the event date (ISO YYYY-MM-DD).
`date_from`	No	Optional inclusive lower bound on the event date (ISO YYYY-MM-DD).
`event_types`	No	Optional 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_types`	No	Optional filter on news_event.impact_type. Valid values: positive, neutral, negative, mixed. Case-insensitive.
`cursor_event_id`	No	Opaque pagination cursor part 1 (the last event id) from the next_cursor returned by a prior call; pass both cursor parts together.
`cursor_published_at`	No	Opaque 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

Name	Required	Description
`count`	Yes
`limit`	Yes
`events`	Yes
`filters`	Yes
`issuer_name`	Yes
`issuer_uuid`	Yes
`next_cursor`	Yes
`company_name`	Yes
`company_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.
`requested_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.
`requested_entity_type`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed34 schema fields changedSep 11, 2026
- removedOutput schema / properties / events / items / properties / article_url / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / events / items / properties / article_url / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / events / items / properties / confidence / anyOf
```
Removed value: -[
-  {
-    "type": "number"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / events / items / properties / confidence / type
```
Added value: +[
+  "number",
+  "null"
+]
```
- removedOutput schema / properties / events / items / properties / event_type / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / events / items / properties / event_type / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / events / items / properties / impact_type / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / events / items / properties / impact_type / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / events / items / properties / links / items / properties / display_name / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / events / items / properties / links / items / properties / display_name / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / events / items / properties / links / items / properties / match_confidence / anyOf
```
Removed value: -[
-  {
-    "type": "number"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / events / items / properties / links / items / properties / match_confidence / type
```
Added value: +[
+  "number",
+  "null"
+]
```
- removedOutput schema / properties / events / items / properties / links / items / properties / match_reason / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / events / items / properties / links / items / properties / match_reason / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / events / items / properties / links / items / properties / parent_entity_id / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / events / items / properties / links / items / properties / parent_entity_id / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / events / items / properties / links / items / properties / source_name / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / events / items / properties / links / items / properties / source_name / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / events / items / properties / published_at / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / events / items / properties / published_at / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / events / items / properties / source / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / events / items / properties / source / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / events / items / properties / summary / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / events / items / properties / summary / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / events / items / properties / title / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / events / items / properties / title / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / filters / properties / date_from / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / filters / properties / date_from / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / filters / properties / date_to / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / filters / properties / date_to / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / issuer_name / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / issuer_name / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / next_cursor / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / next_cursor / type
```
Added value: +[
+  "string",
+  "null"
+]
```
AddedJul 2, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already declare readOnlyHint and idempotentHint, so the safety profile is covered. The description adds genuine behavioral context beyond that: entity-graph resolution expands the result set to related securities and emissions, results are 'enriched' with aggregated links and tags, and pagination is cursor-based requiring both cursor parts together.

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?

Two dense sentences that front-load the capability and then the input/filter contract; nothing is redundant or decorative. Some length is spent enumerating the entity graph, but that enumeration is what makes the scope unambiguous.

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 an 8-parameter read tool with an output schema (so return shape needn't be described), the description covers scope, accepted id types, filters, and pagination. The only thin spot is the absence of explicit guidance on when to prefer this over name/ticker search, which is minor given the schema directs users to search_by_name for id discovery.

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%, including the opaque-hex nature of uuid, enumerated event_types/impact_types values, date bounds, limit range, and the two-part cursor contract. The description only restates the filter categories, adding no syntax or semantics beyond the schema, so the baseline 3 applies.

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 a specific verb and resource ('List full published news events') and names the exact scope: a company's or issuer's full entity graph including security issuers, bonds/shares, and emissions. This distinguishes it from the sibling list tools (bond_list, company_list, share_list), which enumerate entities rather than news about them.

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?

Clearly states the accepted input ('a company OR issuer TokenBel id') and that it resolves the entity itself, which tells the agent it can pass either id type without pre-resolution. It does not state exclusions or contrast with a narrower alternative, but no sibling offers a competing news capability, so the routing ambiguity is low.

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

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?