Skip to main content
Glama

TokenBel Financial Data

entity_news_list

Read-onlyIdempotent

List published news across a company/issuer and linked securities; returns events with links, tags and next_cursor. Filter by event/impact type or date. Example: {"uuid":"f2c03989","impact_types":["negative"]}.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
uuidYesTokenBel id (usually 8 hex chars, no hyphens; not an RFC UUID). Company or issuer id from search_by_name.
limitNoPage size; default 20 (max 50).
date_toNoInclusive event date end (YYYY-MM-DD).
date_fromNoInclusive event date start (YYYY-MM-DD).
event_typesNoTypes (case-insensitive): 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.
impact_typesNoImpact types: positive, neutral, negative, mixed; case-insensitive.
cursor_event_idNoNumeric event ID before | in next_cursor; pass with cursor_published_at.
cursor_published_atNoSort timestamp after | in next_cursor; pass with cursor_event_id.

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changed
    • changedInput schema / properties / cursor_event_id / description
      Previous value: -"Opaque pagination cursor part 1 (the last event id) from the next_cursor returned by a prior call; pass both cursor parts together."New value: +"Numeric event ID before | in next_cursor; pass with cursor_published_at."
    • changedInput schema / properties / cursor_published_at / description
      Previous value: -"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."New value: +"Sort timestamp after | in next_cursor; pass with cursor_event_id."
    • changedInput schema / properties / date_from / description
      Previous value: -"Optional inclusive lower bound on the event date (ISO YYYY-MM-DD)."New value: +"Inclusive event date start (YYYY-MM-DD)."
    • changedInput schema / properties / date_to / description
      Previous value: -"Optional inclusive upper bound on the event date (ISO YYYY-MM-DD)."New value: +"Inclusive event date end (YYYY-MM-DD)."
    • changedInput schema / properties / event_types / description
      Previous value: -"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."New value: +"Types (case-insensitive): 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."
    • changedInput schema / properties / impact_types / description
      Previous value: -"Optional filter on news_event.impact_type. Valid values: positive, neutral, negative, mixed. Case-insensitive."New value: +"Impact types: positive, neutral, negative, mixed; case-insensitive."
    • changedInput schema / properties / limit / description
      Previous value: -"Max results per page (default 20, max 50)."New value: +"Page size; default 20 (max 50)."
    • changedInput schema / properties / uuid / description
      Previous value: -"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."New value: +"TokenBel id (usually 8 hex chars, no hyphens; not an RFC UUID). Company or issuer id from search_by_name."
  2. Changed34 schema fields changed
    • 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"
      +]
  3. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and idempotentHint=true. The description adds further behavioral context: it returns events with links, tags and next_cursor, supports filtering by event/impact type or date, and implies no side effects. This goes beyond the annotation-only safety profile, though it doesn't describe cursor-handling edge cases or error behavior.

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?

The description is compact and effective: a purpose sentence, a return/filter sentence, and one concrete example. It is front-loaded with the most important information and contains no redundant restatement of schema fields.

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 rich input schema, output schema, and read-only annotations, the description is complete enough for an agent to call the tool correctly. It explains the broad behavior, mentions pagination via next_cursor, describes available filter dimensions, and provides an example; the remaining details are covered by the structured schema.

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 the schema already documents all parameters in detail, including uuid format, limit behavior, date formats, enum-like allowed values, and cursor pairing. The description adds only a high-level filter summary and a compact JSON example, which is helpful but not substantial additional semantic meaning.

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 opens with a clear verb and resource: 'List published news across a company/issuer and linked securities.' It also specifies the return content ('events with links, tags and next_cursor'), making the tool's purpose unmistakable and easily distinguished from the sibling market-data and search tools.

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

Usage Guidelines3/5

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

The description clearly implies when to use the tool: when an agent needs published news for a company/issuer and its linked securitiescars. However, it does not explicitly state when to prefer it over alternatives or when not to use it, and it relies on the schema to mention that the uuid comes from search_by_name.

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.

Resources