A
licenseNot graded
qualityD
maintenanceRead-only MCP server providing access to Belarusian securities data: tokens, shares, bonds, companies, ticker search, and company name or UNP search.
MIT
TokenBel Financial Data
Server Details
Read-only MCP server for Belarusian securities: tokens, shares, bonds, companies.
If you are the author of this connector, you can claim ownership with GitHub, an HTTP challenge, or a DNS record. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
- Status
- Healthy
- Uptime
- 100.0% over 38 days
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-11-25
- URL
TDQS
A3.9/5.0
Scored across 19 tools
Disambiguation4/5
Tools are largely distinct by asset class and operation, with clear separation between general list tools and company-scoped list tools. A few pairs (bond_list vs company_bonds_list, share_list vs company_shares_list, token_list vs company_tokens_list) could be confused, but descriptions clarify the difference.
Naming Consistency4/5
Nearly all tools use snake_case with a consistent [resource]_[action] pattern (e.g. bond_get_by_uuid, company_list). The only deviation is search_by_name/search_by_ticker using a verb-first form, but it is minor and predictable.
Tool Count3/5
19 tools is on the heavy side for this server, especially with parallel list tools for bonds, shares, and tokens at both general and company-scoped levels. Coverage is broad but some redundancy pushes it into the borderline-heavy range.
Completeness4/5
The surface covers search, entity lookup, financials, news, FX, and trading stats across bonds, shares, and tokens, which is strong for a read-only financial data API. Gaps include no dedicated issuer detail tool, no bond payout schedule (explicitly noted), and no token payout history.
Available Tools
19 toolsbond_get_by_uuidARead-onlyIdempotentInspect
Get a single BCSE exchange-listed bond by its TokenBel internal identifier (field name: uuid). Returns ticker, issuer_uuid/issuer_name, bond_kind, current coupon/annual yield rate, payment type, maturity date, and is_trading (traded today). Use search_by_ticker first when starting from a ticker. Trading history is available via trading_stats_get; no separate bond payout schedule is exposed by this worker.
ParametersJSON 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. Bond id, usually discovered via search_by_ticker. |
Output Schema
ParametersJSON Schema
| Name | Required | Description |
|---|---|---|
| name | Yes | |
| 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. |
| ticker | Yes | |
| currency | Yes | |
| bond_kind | Yes | |
| is_active | Yes | |
| created_at | Yes | |
| is_trading | Yes | |
| updated_at | Yes | |
| issuer_name | Yes | |
| issuer_uuid | Yes | |
| percent_rate | Yes | |
| maturity_date | Yes | |
| nominal_value | Yes | |
| security_kind | Yes | |
| admission_date | Yes | |
| percent_payment_type | Yes |
TDQS
A4.4/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 real behavioral context beyond that: the exact fields returned, the semantics of is_trading ('traded today'), and a genuine scope limit ('no separate bond payout schedule is exposed by this worker'). It stops short of describing pagination or error behavior, but for a single-record read that is minor.
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?
Front-loaded with the core action and identifier, then compactly layers in the sibling routing and scope limits across three sentences. The enumeration of return fields is slightly redundant with the output schema but still readable and earned by the routing value around it.
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?
With an output schema present the description doesn't need to enumerate return fields, yet it costs little and the agent additionally gets identifier provenance, the sibling prerequisite, history/payout routing, and the trading-today semantics. Nothing needed to call this correctly is missing.
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%, and the schema already spells out that uuid is an opaque 8-char hex identifier discoverable via search_by_ticker. The description's 'TokenBel internal identifier (field name: uuid)' largely restates the schema, adding only the terminology mapping, 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 (Get) and resource (a single BCSE exchange-listed bond), identifies the exact identifier used (TokenBel internal identifier / uuid field), and names the sibling (search_by_ticker) that produces that identifier. An agent can distinguish it from bond_list and the *_get_by_uuid siblings immediately.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines5/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
Explicitly routes the agent: 'Use search_by_ticker first when starting from a ticker,' and points to trading_stats_get for trading history while stating that no payout schedule exists. Both the when-to-use and the alternative routes are named rather than left to inference.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
bond_listARead-onlyIdempotentInspect
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.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| 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
ParametersJSON Schema
| Name | Required | Description |
|---|---|---|
| bonds | Yes | |
| count | Yes | |
| next_cursor | Yes |
TDQS
A3.5/5.0
Behavior3/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 that pagination is cursor-based and that results are limited to active listings, but the schema itself already documents the cursor parameters, so the incremental behavioral value is modest.
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 purpose is front-loaded in the first clause, followed by filter and pagination notes in two compact sentences. Nearly every phrase earns its place, though the parameter-name restatement adds minor redundancy.
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?
An output schema exists, so return values need not be explained, and the description covers purpose, filters, and pagination. It is largely complete for a read-only filtered-list tool, with only the sibling differentiation gap remaining.
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 all five parameters are already documented in the schema, establishing a baseline of 3. The description restates the issuer_uuid and is_trading filters and the search_by_name linkage, but adds little beyond what the schema descriptions already contain.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose4/5
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb (List) plus resource and scope (active BCSE exchange-listed bonds), which is more precise than a generic list tool. It names its optional filters, but does not differentiate itself from the sibling company_bonds_list, leaving the agent to infer which bond listing to use.
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 gives a useful acquisition hint (take issuer_uuid from search_by_name results where entity_type="issuer"), which implies usage context. However, it offers no explicit when-to-use vs. when-not-to-use guidance or alternatives against company_bonds_list or share_list.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
company_bonds_listARead-onlyIdempotentInspect
List summary cards of a company's active bonds. Accepts a company OR issuer TokenBel id; resolves the company and returns its bonds.
ParametersJSON 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. Company or issuer id, usually discovered via search_by_name. | |
| limit | No | Max results per page (default 50). | |
| 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. Opaque cursor id part from the next_cursor returned by a prior call; pass both cursor parts together. | |
| cursor_created_at | No | Opaque cursor datetime part (ISO 8601) from the next_cursor returned by a prior call; pass both cursor parts together. |
Output Schema
ParametersJSON Schema
| Name | Required | Description |
|---|---|---|
| bonds | Yes | |
| count | Yes | |
| limit | 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 |
TDQS
A3.6/5.0
Behavior3/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 genuinely useful behavior beyond that: an issuer id is accepted and resolved into a company before returning bonds. It does not mention pagination behavior despite the cursor parameters, leaving a gap.
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 short sentences with no waste; the primary action is front-loaded and the id-resolution caveat follows immediately. Every clause carries information an agent needs.
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?
An output schema exists, so return values need not be explained, and the schema documents all four parameters including pagination. The description covers purpose and the company/issuer id resolution, leaving only minor gaps such as paging expectations.
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 fully documents uuid, limit, and both cursor parts. The description's note that uuid may be a company OR issuer id largely restates the schema's 'Company or issuer id' text, adding little new meaning, so baseline 3 applies.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose4/5
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb and resource ('List summary cards of a company's active bonds'), and narrows scope to active bonds for a single company, which implicitly separates it from the broader bond_list. It does not name a sibling explicitly, so it stays at 4 rather than 5.
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 second sentence signals the trigger condition (you have a company OR issuer id) and notes the id is resolved to a company, which implies when to use it. However, it never states when to prefer this over bond_list or bond_get_by_uuid, nor any exclusion, so guidance is only implied.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
company_financial_params_getARead-onlyIdempotentInspect
Get financial parameters for a company or securities issuer by TokenBel internal identifier (field name: uuid). Returns periodic financial statement metrics (balance, equity, long/short-term assets and liabilities) and calculated financial ratios (liquidity, leverage, independence, stability, capitalization). Accepts a company id or an issuer id — issuer ids are resolved to their linked company. Find the id via search_by_name first.
ParametersJSON 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. Company or issuer id, usually discovered via search_by_name. | |
| limit_periods | No | Max number of periods to return (newest first). Default 8. |
Output Schema
ParametersJSON Schema
| Name | Required | Description |
|---|---|---|
| count | Yes | |
| periods | Yes | |
| issuer_name | Yes | |
| issuer_uuid | 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 |
TDQS
A4/5.0
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint and idempotentHint, so safety is covered. The description adds genuine non-obvious behavior: issuer ids are silently resolved to their linked company, and results are periodic (series, not a single snapshot), which an agent needs to interpret results correctly.
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?
Three sentences, front-loaded: purpose and identifier first, then contents, then the id-discovery hint. Dense with terms but every sentence carries information; no filler.
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?
With an output schema present, the return values need not be spelled out, and both parameters are fully described in-schema with annotations covering the safety profile. Nothing an agent needs to call this correctly or interpret results is missing.
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 both parameters (uuid format, limit_periods min/max/default) are already fully documented in the schema. The description restates the uuid as the internal identifier and its discovery path, adding little beyond what the schema text already says, so baseline 3 applies.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose4/5
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb ('Get') and resource ('financial parameters for a company or securities issuer') and then enumerates exactly what comes back: periodic balance/equity/asset/liability metrics plus calculated ratios (liquidity, leverage, independence, stability, capitalization). That content list effectively distinguishes it from company_get_by_uuid, though it never names a sibling explicitly.
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?
Gives clear routing context — 'Find the id via search_by_name first' and the note that issuer ids are accepted and resolved — so an agent knows the prerequisite step. It stops short of explicit when-not-to-use or a direct comparison against company_get_by_uuid / the other company_* list tools.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
company_get_by_uuidARead-onlyIdempotentInspect
Get a single company catalogue row by its TokenBel internal identifier (field name: uuid). Returns name, full_name, UNP (Belarusian tax ID), industry, logo, and activity flag. Companies are not always the same row as securities issuers; use search_by_name to discover both companies and issuers.
ParametersJSON 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. Company id, usually from search_by_name entity_type="company". |
Output Schema
ParametersJSON Schema
| Name | Required | Description |
|---|---|---|
| unp | Yes | |
| name | Yes | |
| 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. |
| address | Yes | |
| industry | Yes | |
| full_name | Yes | |
| is_active | Yes | |
| logo_path | Yes | |
| created_at | Yes | |
| updated_at | Yes |
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 safety is covered. The description adds real behavioral context: the exact set of returned fields and the semantic caveat that a company row is not necessarily the same entity as a securities issuer, which prevents an agent from conflating the two namespaces. It does not describe behavior when the id is absent (null vs error), leaving a minor gap.
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?
Three tight sentences, front-loaded with the verb and key field, then returns, then the disambiguation note. The returned-field enumeration is partly redundant given an output schema exists, which slightly dilutes it, but nothing is padding.
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 a single-param read tool with an output schema and clear annotations, the description covers what it retrieves, how to obtain the id, and how it differs from issuer lookups. The only omission is explicit not-found/error behavior, which is minor and often unnecessary on a standard catalogue read.
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% and the uuid property description already explains that it is an opaque 8-char hex string, not an RFC UUID, and where it comes from. The description only restates the identifier and its source, adding no syntax or format detail 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 ('Get a single company catalogue row by its TokenBel internal identifier'), names the key field (uuid), and enumerates the returned attributes. The closing note that companies are not always the same row as securities issuers distinguishes it from share_get_by_uuid / bond_get_by_uuid.
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?
Tells the agent where the identifier comes from ('use search_by_name to discover both companies and issuers'), which is the key prerequisite for calling this tool. It does not explicitly contrast with company_list (browse all) or state the failure mode when the id is unknown, so it stops short of full when/when-not guidance.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
company_listARead-onlyIdempotentInspect
List active company catalogue rows with optional filtering by industry. This does not list security_issuer rows directly; use search_by_name to find issuers and then share_list/bond_list with issuer_uuid. Supports cursor-based pagination.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Max results (1-1000, default 50) | |
| industry | No | Filter by company_industry.name exact value | |
| 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. | |
| cursor_created_at | No | Pagination cursor datetime (ISO 8601) |
Output Schema
ParametersJSON Schema
| Name | Required | Description |
|---|---|---|
| count | Yes | |
| companies | 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, so the safety profile is covered; the description adds the pagination behavior ('cursor-based') and the scope limitation regarding issuer rows. It does not discuss rate limits, ordering guarantees, or result-count behavior, but with annotations and an output schema present the remaining burden is light.
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?
Three short sentences, front-loaded with the primary purpose before the exclusion and pagination notes. Slightly more text is spent on the issuer redirection than strictly needed, but every clause carries information.
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?
With a full schema, output schema, and annotations, the description supplies everything an agent needs to select and invoke it: scope, the negative scope, the alternative path, and pagination. Only minor details (default page size, ordering) are absent, and those are visible in the 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 all four parameters (limit, industry, cursor_uuid, cursor_created_at) are already documented in the schema, including the non-obvious uuid-format caveat for cursor_uuid. The description only restates the industry filter, adding no new parameter semantics — 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 active company catalogue rows') plus an optional filter, and explicitly names what it is not ('does not list security_issuer rows directly'). An agent can distinguish it from share_list/bond_list/search_by_name without opening any schema.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines5/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
Gives an explicit routing rule for the issuer case: use search_by_name first, then share_list/bond_list with issuer_uuid. That is a concrete when-to-use-this-vs-alternative instruction rather than an implied one.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
company_tokens_listARead-onlyIdempotentInspect
List summary cards of a company's active tokens (emissions). Accepts a company OR issuer TokenBel id; resolves the company and returns its tokens.
ParametersJSON 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. Company or issuer id, usually discovered via search_by_name. | |
| limit | No | Max results per page (default 50). | |
| 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. Opaque cursor id part from the next_cursor returned by a prior call; pass both cursor parts together. | |
| cursor_created_at | No | Opaque cursor datetime part (ISO 8601) from the next_cursor returned by a prior call; pass both cursor parts together. |
Output Schema
ParametersJSON Schema
| Name | Required | Description |
|---|---|---|
| count | Yes | |
| limit | Yes | |
| tokens | 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 |
TDQS
A3.5/5.0
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true and idempotentHint=true, so the safety profile is covered. The description adds that the tool resolves the company from either a company or issuer id and that only 'active' tokens are returned, which is genuine behavioral context, but it is thin and overlaps with the uuid schema note.
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 short sentences, front-loaded with the core action and scope, with the resolution detail second. Efficient, though the second sentence partially duplicates the uuid parameter description.
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?
An output schema exists, so return values need not be described, and annotations cover safety and idempotency. The description is adequate for a paginated read tool, but it omits whether inactive tokens exist and how this differs from the sibling token_list, which an agent selecting among list tools would want.
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 four parameters, including the company-or-issuer nature of uuid and the two-part cursor. The description restates the company/issuer id flexibility but adds no syntax, format, or defaulting detail beyond the schema; baseline 3 applies.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose4/5
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb (List) and resource (a company's active tokens/emissions) plus the scope qualifier 'active'. It is clearly different from company_bonds_list and company_shares_list by resource type, but it never explicitly reconciles with the sibling token_list, leaving the token_list vs company_tokens_list relationship to inference.
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 implies when to use it (you have a company or issuer TokenBel id and want that entity's tokens), and it notes that the id may be a company or an issuer. However, it gives no explicit when-not guidance and never routes the agent to token_list for unfiltered queries or to search_by_name for discovering the id, despite search_by_name being a sibling.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
currency_rate_getARead-onlyIdempotentInspect
Get NBRB (National Bank of Belarus) official FX rates against BYN (Belarusian ruble) for USD, EUR, and/or RUB. Rates are BYN per 1 unit of foreign currency. Modes: latest (no dates), single_date (date), range (date_from/date_to, either bound optional), or grouped weekly/monthly aggregates (group_by + range). Only usd/eur/rub are supported; BYN is the implicit base currency.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| date | No | Single date in YYYY-MM-DD format. Mutually exclusive with date_from/date_to. | |
| date_to | No | Range end date in YYYY-MM-DD format (inclusive, >= date_from). Open-ended or today-bounded ranges bypass cache. | |
| currency | No | Filter to one supported foreign currency: usd, eur, or rub. Omit to return all three. BYN is the base currency, not a target. | |
| group_by | No | Aggregate by week or month. Requires a date range (date_from/date_to), not a single date. | |
| date_from | No | Range start date in YYYY-MM-DD format (inclusive). Can be omitted for open-start range. |
Output Schema
ParametersJSON Schema
| Name | Required | Description |
|---|---|---|
| mode | Yes | |
| count | Yes | |
| date_to | Yes | |
| results | Yes | |
| currency | Yes | |
| group_by | No | |
| date_from | Yes | |
| base_currency | Yes |
TDQS
A4.3/5.0
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already cover the safety profile (readOnlyHint, idempotentHint), so the description is free to add domain behavior, and it does: the BYN-per-unit quote direction, BYN as implicit base, and the restriction to only usd/eur/rub. It adds no auth, rate-limit, or error behavior, which keeps it out of 5 territory.
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?
Four tight sentences with the highest-value facts (source, quote convention, mode selection, currency constraint) front-loaded and no filler. Every clause carries information an agent needs to construct a call.
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?
With an output schema present, return values need no explanation, and the description fully covers the mode selection, parameter dependencies, currency constraints, and base-currency convention. Nothing an agent needs in order to invoke this correctly is missing.
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 each parameter already carries its own format, exclusivity, and dependency notes in the schema. The description's mode taxonomy largely restates those combinations rather than adding syntax or defaults the schema lacks, so the baseline of 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+resource (get NBRB official FX rates against BYN) and pins the exact supported currency set, so it cannot be confused with any of the sibling bond/share/company/news tools. The quote convention 'BYN per 1 unit of foreign currency' removes the main ambiguity an agent would otherwise face.
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 enumerates the four usage modes (latest, single_date, range, grouped) and the parameter combination that selects each, which is real when-to-use guidance. It does not state exclusions or edge cases (e.g., how far back NBRB data goes, behavior on non-business days), so it stops short of a 5.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
entity_news_listARead-onlyIdempotentInspect
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.
ParametersJSON 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. 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
ParametersJSON 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 |
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.
search_by_nameARead-onlyIdempotentInspect
Search companies AND securities issuers by name, full name, or UNP (Belarusian tax ID). Results are tagged with entity_type: "company" (use company_get_by_uuid) or "issuer" (use uuid as issuer_uuid in share_list/bond_list). The returned uuid/issuer_uuid values are opaque TokenBel internal ids (usually 8 hex chars, not RFC UUIDs). Companies and issuers are different tables and may overlap; linked_company_uuid connects an issuer to a company when known.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Max results (1-100, default 20) | |
| query | Yes | Company/issuer name or UNP (Belarusian tax ID) search query; case-insensitive, e.g. 'bank' matches 'MTBank', 'Priorbank' |
Output Schema
ParametersJSON Schema
| Name | Required | Description |
|---|---|---|
| count | Yes | |
| query | Yes | |
| results | Yes |
TDQS
A4.6/5.0
Behavior5/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations only cover read-only/idempotent safety, but the description adds substantial non-obvious behavior: the returned uuids are opaque TokenBel internal ids (typically 8 hex chars, not RFC UUIDs), companies and issuers live in different tables that may overlap, and linked_company_uuid bridges the two when known.
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?
Three dense sentences with no filler; the search scope is front-loaded and the downstream routing and id caveats follow in priority order. Slightly packed, but every clause carries information an agent needs.
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?
An output schema exists so return values need no prose, and the description still covers the two things an agent must know to act on results: what the uuids actually are and how issuers relate to companies. Nothing material is missing for a read-only 2-param search.
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 already 100%, so the baseline is 3, but the description adds that matching covers full name in addition to name and UNP, and clarifies the entity_type tagging semantics of the result set. It stops short of documenting the limit parameter, which the schema already handles.
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 dual resource ('search companies AND securities issuers') plus the match keys (name, full name, UNP), which cleanly separates it from search_by_ticker. An agent knows exactly what this returns without opening the schema.
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?
Explicitly routes results downstream: entity_type 'company' → company_get_by_uuid, 'issuer' → issuer_uuid in share_list/bond_list. It does not explicitly state when to prefer search_by_ticker over this tool, so the name-vs-ticker boundary is left to inference.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
search_by_tickerARead-onlyIdempotentInspect
Search BCSE exchange-listed shares and bonds by ticker (case-insensitive substring match). Tokens are excluded because they do not have ticker symbols. Use the returned uuid value as an opaque TokenBel internal id (usually 8 hex chars, not an RFC UUID) with share_get_by_uuid/bond_get_by_uuid, share_payouts_get for share rows, or trading_stats_get for either share/bond row. Returns entity_type, ticker, issuer_uuid, issuer_name, and is_trading (traded today).
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Max results (1-100, default 20) | |
| query | Yes | Ticker search query for listed shares/bonds only (case-insensitive substring, e.g. 'MTB' matches 'MTBank') |
Output Schema
ParametersJSON Schema
| Name | Required | Description |
|---|---|---|
| count | Yes | |
| query | Yes | |
| results | Yes |
TDQS
A4.2/5.0
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint and idempotentHint, so safety is covered; the description still adds real value by warning that the returned uuid is an opaque TokenBel internal id (usually 8 hex chars, not an RFC UUID) and by defining is_trading as 'traded today'. It does not mention pagination behavior beyond limit, which is minor.
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?
Three dense sentences, front-loaded with purpose and the token exclusion before the follow-up routing. Every clause carries information, though the trailing return-field list is partly redundant given the output schema and adds length without new knowledge.
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?
For a two-parameter read tool with full schema coverage, annotations, and an output schema, the description covers what the search matches, what it excludes, and how to chain the returned id into the correct downstream tool. Nothing an agent needs to invoke it correctly is missing.
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 is 3. The description's 'case-insensitive substring match' and token exclusion duplicate what the query parameter description already states ('case-insensitive substring, e.g. MTB matches MTBank'), adding no new syntax or semantics for query or limit.
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 (Search), the resource (BCSE exchange-listed shares and bonds), the matching mode (case-insensitive substring on ticker), and an explicit exclusion (tokens, because they lack tickers). An agent can distinguish it from search_by_name and the *_list siblings immediately.
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?
Gives concrete downstream routing: use the returned uuid with share_get_by_uuid/bond_get_by_uuid, share_payouts_get for share rows, or trading_stats_get for either. This tells the agent what to do after a hit, but it never states when to prefer this over sibling search tools like search_by_name, so it falls short of explicit alternatives.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
token_get_by_uuidARead-onlyIdempotentInspect
Get a single token by its TokenBel internal identifier (field name: uuid). Tokens are TokenBel-native tokenized corporate securities on fintech platforms (fainex/finstore/bynex/whitebird), not BCSE-listed tickers. Returns platform, lifecycle status, pricing, coupon rate, and company info.
ParametersJSON 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. Token id, usually discovered via token_list. |
Output Schema
ParametersJSON Schema
| Name | Required | Description |
|---|---|---|
| name | Yes | |
| sold | Yes | |
| 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. |
| status | Yes | |
| currency | Yes | |
| platform | Yes | |
| is_active | Yes | |
| created_at | Yes | |
| updated_at | Yes | |
| token_price | Yes | |
| company_name | Yes | |
| company_uuid | Yes | |
| percent_rate | Yes | |
| total_tokens | Yes | |
| emission_stop | Yes |
TDQS
A3.7/5.0
Behavior3/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 useful domain context (token vs ticker) but its return-field list (platform, status, pricing, coupon, company) is largely redundant with the output schema, so added value is modest.
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?
Three short sentences, front-loaded with the action and identifier, then the disambiguation. Mostly earns its place, though the trailing 'returns ...' sentence overlaps with the existing output schema.
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?
With an output schema, full param coverage, and read-only/idempotent annotations, the definition supplies all an agent needs to invoke it correctly, plus the token-vs-ticker disambiguation. Minor missing piece is explicit routing to token_list for id discovery, which lives only in the 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% and the uuid parameter is documented in depth (opaque hex, ~8 chars, not an RFC UUID). The description only restates 'field name: uuid', so it adds little beyond the schema; baseline 3 is appropriate.
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 (Get) and resource (a single token) keyed on a named identifier field, and disambiguates 'token' by explaining it is a TokenBel-native tokenized security rather than a BCSE ticker. An agent can distinguish this from bond_get_by_uuid/share_get_by_uuid and from token_list without opening any schema.
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?
Usage is only implied: the description defines what a token is and the schema notes the id is 'usually discovered via token_list', but the description itself gives no explicit when-to-use vs alternative (e.g., token_list, token_trading_stats_get) or prerequisites. Adequate but with clear gaps.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
token_listARead-onlyIdempotentInspect
List active tokens with optional filtering by fintech platform and token lifecycle status. Tokens do not have tickers; use this list tool to browse tokenized securities by platform/status. Supports cursor-based pagination.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Max results (1-1000, default 50) | |
| status | No | Filter by token lifecycle status: SELL_NOT_STARTED (sale not open yet), SELL_IN_PROGRESS (currently selling), SELL_SUSPENDED (sale paused), SOLD_OUT (fully sold), SELL_ENDED (sale ended), CIRCULATION_ENDED (matured/circulation ended), OBLIGATIONS_COMPLETED (issuer obligations completed). | |
| platform | No | Filter by tokenization platform: fainex, finstore, bynex, or whitebird. | |
| 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. | |
| cursor_created_at | No | Pagination cursor datetime (ISO 8601) |
Output Schema
ParametersJSON Schema
| Name | Required | Description |
|---|---|---|
| count | Yes | |
| tokens | Yes | |
| next_cursor | Yes |
TDQS
A3.9/5.0
Behavior3/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 by structured data. The description adds cursor-based pagination behavior, which is genuinely beyond the annotations, but the qualifier 'active tokens' sits awkwardly against the status enum that includes terminal states (SELL_ENDED, CIRCULATION_ENDED), leaving the returned scope slightly ambiguous.
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?
Three compact sentences, front-loaded with the purpose and filtering capability, then the ticker caveat, then pagination. Efficient overall, though the pagination sentence is a slightly detached tack-on rather than integrated into the browsing guidance.
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?
With a full output schema, rich annotations, and 100%-documented parameters, the description only needs to frame purpose and scoping, which it does. The one remaining gap is the meaning of 'active' given the terminal status values offered as filters.
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%: limit, status (with per-value explanations), platform, and both cursor fields are fully documented in the schema itself. The description adds no parameter-level syntax, defaults, or interplay (e.g., how the two cursor fields pair), so this is the baseline 3 case where structured data does the lifting.
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 active tokens') plus the two filter axes (platform, lifecycle status), and explicitly notes that tokens lack tickers, distinguishing this tool from the ticker-driven search_by_ticker/share_list/bond_list siblings. An agent can identify this as the browse-tokenized-securities entry point without opening a schema.
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?
Gives clear usage context: use this list tool to browse tokenized securities by platform/status, implicitly steering agents away from ticker-based lookups. However it never names an explicit alternative (e.g., token_get_by_uuid for a single token, company_tokens_list for company-scoped results) or states when not to use it, so exclusion guidance is absent.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
token_trading_stats_getARead-onlyIdempotentInspect
Get primary-market sales statistics for a token by its TokenBel internal identifier (field name: uuid). Returns a per-day series of tokens sold (derived from the cumulative instrument_log.sold counter), range totals, and a token snapshot (status, token_price, percent_rate, sold_total, total_tokens, sold_pct). Find the id via token_list first. Always a date range: omit both dates for the last 30 days, or provide date_from and/or date_to. Secondary-market data is not included.
ParametersJSON 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. Token id, usually discovered via token_list. | |
| date_to | No | Range end date YYYY-MM-DD (inclusive, >= date_from). Defaults to today when omitted. | |
| date_from | No | Range start date YYYY-MM-DD (inclusive). Defaults to date_to minus 30 days when omitted. |
Output Schema
ParametersJSON Schema
| Name | Required | Description |
|---|---|---|
| mode | Yes | |
| 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. |
| daily | Yes | |
| period | Yes | |
| totals | Yes | |
| currency | Yes | |
| platform | Yes | |
| snapshot | Yes | |
| security_kind | Yes |
TDQS
A4.5/5.0
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint and idempotentHint, so safety is covered. The description adds real behavioral context beyond that: the per-day series is derived from the cumulative instrument_log.sold counter, the date defaults, and the explicit exclusion of secondary-market data.
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?
Front-loaded with the core action, then ordered by identifier discovery, date-range rules, and scope exclusion. Dense but every sentence carries information; no filler.
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?
For a read-only stats tool with a full schema and an output schema, nothing an agent needs to call it correctly is missing: the id source, date semantics, and scope boundary are all present. Return-value detail is a bonus rather than a requirement given the output 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 all three parameters are already documented in the schema, making 3 the baseline. The description mostly restates the date-range defaults already present in the schema, adding only the 'field name: uuid' hint.
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 (get primary-market sales statistics for a token) plus the identifier it keys on. It explicitly carves out scope by saying secondary-market data is not included, which cleanly separates it from the sibling trading_stats_get.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines5/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
Gives the prerequisite ('Find the id via token_list first'), the default behavior ('omit both dates for the last 30 days'), and the alternative usage ('provide date_from and/or date_to'). It also names the exclusion condition (secondary-market data) that routes the agent elsewhere.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
trading_stats_getARead-onlyIdempotentInspect
Get trading statistics for a BCSE exchange-listed share or bond by TokenBel internal identifier (field name: uuid). Use search_by_ticker first. Modes: latest_30d (default, no dates) reads the refreshed 30-day materialized view and includes latest price/yield plus yield_wavg; range (both date_from and date_to, YYYY-MM-DD, inclusive) aggregates raw trade history live and returns yield_min/yield_max only — yield_wavg and all *_latest fields are null in range mode. Omit both dates or provide both; one bound is rejected. Both modes also return daily_series: one point per trade_date (same-day buckets collapsed across market_type/trade_mode/payment_code) with per-day turnover, transactions, price_wavg/min/max, and yield_min/max — no range-level rollup.
ParametersJSON 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. Listed share or bond id, usually discovered via search_by_ticker. | |
| date_to | No | Range end date YYYY-MM-DD (inclusive, >= date_from). Provide both date_from and date_to for range mode; ranges ending today bypass cache. | |
| date_from | No | Range start date YYYY-MM-DD (inclusive). Provide both date_from and date_to for range mode; omit both for latest_30d mode. |
Output Schema
ParametersJSON Schema
| Name | Required | Description |
|---|---|---|
| mode | Yes | |
| 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. |
| period | Yes | |
| ticker | Yes | |
| price_max | Yes | |
| price_min | Yes | |
| yield_max | Yes | |
| yield_min | Yes | |
| price_wavg | Yes | |
| yield_wavg | Yes | |
| daily_series | Yes | |
| trading_days | Yes | |
| security_kind | Yes | |
| last_trade_date | Yes | |
| turnover_amount | Yes | |
| price_latest_date | Yes | |
| price_wavg_latest | Yes | |
| yield_latest_date | Yes | |
| yield_wavg_latest | Yes | |
| transactions_count | Yes |
TDQS
A4.6/5.0
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint and idempotentHint, but the description goes well beyond them: it discloses which fields are null in range mode (yield_wavg, *_latest), that ranges ending today bypass cache, that range mode aggregates raw history live, and that daily_series is bucketed per trade_date with no range-level rollup. This is substantial behavioral context; only pagination/volume limits on large ranges are left unstated.
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?
Front-loaded with purpose, then usage, then mode semantics in one dense paragraph. Every clause carries distinct information (modes, null-field behavior, bucketing) with no filler, though the single unbroken block is heavier than an agent-optimized bulleted structure would be.
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?
Despite an output schema existing, the description still previews the key return shapes (latest price/yield, yield_wavg, yield_min/max, daily_series fields) that differ by mode — exactly the case where the schema alone would not tell an agent which mode to pick. Nothing needed to invoke it correctly is missing.
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% so the baseline is 3, but the description adds real meaning beyond the schema: date_from/date_to are mutually required as a pair ('omit both or provide both'), YYYY-MM-DD is inclusive, and the date format drives which mode executes. It does not restate the uuid definition, which the schema already covers well.
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 ('Get trading statistics for a BCSE exchange-listed share or bond') plus the exact key field ('uuid'). It clearly separates this tool from sibling token_trading_stats_get (tokens) and the share/bond getters, so the agent can route without opening a schema.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines5/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
Explicitly tells the agent to call search_by_ticker first to discover the identifier, and gives concrete mode-selection rules: latest_30d when no dates are supplied, range only with both bounds, and one bound is rejected. The when-to-use logic is fully specified rather than implied.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
19 tool updates
- Changed
bond_get_by_uuid22 fields changed- removed
Output schema / properties / admission_date / anyOfRemoved value: -[ - { - "type": "string" - }, - { - "type": "null" - } -] - added
Output schema / properties / admission_date / typeAdded value: +[ + "string", + "null" +] - removed
Output schema / properties / bond_kind / anyOfRemoved value: -[ - { - "type": "string" - }, - { - "type": "null" - } -] - added
Output schema / properties / bond_kind / typeAdded value: +[ + "string", + "null" +] - removed
Output schema / properties / currency / anyOfRemoved value: -[ - { - "type": "string" - }, - { - "type": "null" - } -] - added
Output schema / properties / currency / typeAdded value: +[ + "string", + "null" +] - removed
Output schema / properties / is_trading / anyOfRemoved value: -[ - { - "type": "boolean" - }, - { - "type": "null" - } -] - added
Output schema / properties / is_trading / typeAdded value: +[ + "boolean", + "null" +] - removed
Output schema / properties / issuer_name / anyOfRemoved value: -[ - { - "type": "string" - }, - { - "type": "null" - } -] - added
Output schema / properties / issuer_name / typeAdded value: +[ + "string", + "null" +] - removed
Output schema / properties / maturity_date / anyOfRemoved value: -[ - { - "type": "string" - }, - { - "type": "null" - } -] - added
Output schema / properties / maturity_date / typeAdded value: +[ + "string", + "null" +] - removed
Output schema / properties / name / anyOfRemoved value: -[ - { - "type": "string" - }, - { - "type": "null" - } -] - added
Output schema / properties / name / typeAdded value: +[ + "string", + "null" +] - removed
Output schema / properties / nominal_value / anyOfRemoved value: -[ - { - "type": "string" - }, - { - "type": "null" - } -] - added
Output schema / properties / nominal_value / typeAdded value: +[ + "string", + "null" +] - removed
Output schema / properties / percent_payment_type / anyOfRemoved value: -[ - { - "type": "string" - }, - { - "type": "null" - } -] - added
Output schema / properties / percent_payment_type / typeAdded value: +[ + "string", + "null" +] - removed
Output schema / properties / percent_rate / anyOfRemoved value: -[ - { - "type": "string" - }, - { - "type": "null" - } -] - added
Output schema / properties / percent_rate / typeAdded value: +[ + "string", + "null" +] - removed
Output schema / properties / ticker / anyOfRemoved value: -[ - { - "type": "string" - }, - { - "type": "null" - } -] - added
Output schema / properties / ticker / typeAdded value: +[ + "string", + "null" +]
- Changed
bond_list24 fields changed- removed
Output schema / properties / bonds / items / properties / admission_date / anyOfRemoved value: -[ - { - "type": "string" - }, - { - "type": "null" - } -] - added
Output schema / properties / bonds / items / properties / admission_date / typeAdded value: +[ + "string", + "null" +] - removed
Output schema / properties / bonds / items / properties / bond_kind / anyOfRemoved value: -[ - { - "type": "string" - }, - { - "type": "null" - } -] - added
Output schema / properties / bonds / items / properties / bond_kind / typeAdded value: +[ + "string", + "null" +] - removed
Output schema / properties / bonds / items / properties / currency / anyOfRemoved value: -[ - { - "type": "string" - }, - { - "type": "null" - } -] - added
Output schema / properties / bonds / items / properties / currency / typeAdded value: +[ + "string", + "null" +] - removed
Output schema / properties / bonds / items / properties / is_trading / anyOfRemoved value: -[ - { - "type": "boolean" - }, - { - "type": "null" - } -] - added
Output schema / properties / bonds / items / properties / is_trading / typeAdded value: +[ + "boolean", + "null" +] - removed
Output schema / properties / bonds / items / properties / issuer_name / anyOfRemoved value: -[ - { - "type": "string" - }, - { - "type": "null" - } -] - added
Output schema / properties / bonds / items / properties / issuer_name / typeAdded value: +[ + "string", + "null" +] - removed
Output schema / properties / bonds / items / properties / maturity_date / anyOfRemoved value: -[ - { - "type": "string" - }, - { - "type": "null" - } -] - added
Output schema / properties / bonds / items / properties / maturity_date / typeAdded value: +[ + "string", + "null" +] - removed
Output schema / properties / bonds / items / properties / name / anyOfRemoved value: -[ - { - "type": "string" - }, - { - "type": "null" - } -] - added
Output schema / properties / bonds / items / properties / name / typeAdded value: +[ + "string", + "null" +] - removed
Output schema / properties / bonds / items / properties / nominal_value / anyOfRemoved value: -[ - { - "type": "string" - }, - { - "type": "null" - } -] - added
Output schema / properties / bonds / items / properties / nominal_value / typeAdded value: +[ + "string", + "null" +] - removed
Output schema / properties / bonds / items / properties / percent_payment_type / anyOfRemoved value: -[ - { - "type": "string" - }, - { - "type": "null" - } -] - added
Output schema / properties / bonds / items / properties / percent_payment_type / typeAdded value: +[ + "string", + "null" +] - removed
Output schema / properties / bonds / items / properties / percent_rate / anyOfRemoved value: -[ - { - "type": "string" - }, - { - "type": "null" - } -] - added
Output schema / properties / bonds / items / properties / percent_rate / typeAdded value: +[ + "string", + "null" +] - removed
Output schema / properties / bonds / items / properties / ticker / anyOfRemoved value: -[ - { - "type": "string" - }, - { - "type": "null" - } -] - added
Output schema / properties / bonds / items / properties / ticker / typeAdded value: +[ + "string", + "null" +] - removed
Output schema / properties / next_cursor / anyOfRemoved value: -[ - { - "type": "string" - }, - { - "type": "null" - } -] - added
Output schema / properties / next_cursor / typeAdded value: +[ + "string", + "null" +]
- Changed
company_bonds_list20 fields changed- removed
Output schema / properties / bonds / items / properties / bond_kind / anyOfRemoved value: -[ - { - "type": "string" - }, - { - "type": "null" - } -] - added
Output schema / properties / bonds / items / properties / bond_kind / typeAdded value: +[ + "string", + "null" +] - removed
Output schema / properties / bonds / items / properties / currency / anyOfRemoved value: -[ - { - "type": "string" - }, - { - "type": "null" - } -] - added
Output schema / properties / bonds / items / properties / currency / typeAdded value: +[ + "string", + "null" +] - removed
Output schema / properties / bonds / items / properties / is_traded_today / anyOfRemoved value: -[ - { - "type": "boolean" - }, - { - "type": "null" - } -] - added
Output schema / properties / bonds / items / properties / is_traded_today / typeAdded value: +[ + "boolean", + "null" +] - removed
Output schema / properties / bonds / items / properties / maturity_date / anyOfRemoved value: -[ - { - "type": "string" - }, - { - "type": "null" - } -] - added
Output schema / properties / bonds / items / properties / maturity_date / typeAdded value: +[ + "string", + "null" +] - removed
Output schema / properties / bonds / items / properties / nominal_value / anyOfRemoved value: -[ - { - "type": "string" - }, - { - "type": "null" - } -] - added
Output schema / properties / bonds / items / properties / nominal_value / typeAdded value: +[ + "string", + "null" +] - removed
Output schema / properties / bonds / items / properties / percent_payment_type / anyOfRemoved value: -[ - { - "type": "string" - }, - { - "type": "null" - } -] - added
Output schema / properties / bonds / items / properties / percent_payment_type / typeAdded value: +[ + "string", + "null" +] - removed
Output schema / properties / bonds / items / properties / percent_rate / anyOfRemoved value: -[ - { - "type": "number" - }, - { - "type": "null" - } -] - added
Output schema / properties / bonds / items / properties / percent_rate / typeAdded value: +[ + "number", + "null" +] - removed
Output schema / properties / bonds / items / properties / ticker / anyOfRemoved value: -[ - { - "type": "string" - }, - { - "type": "null" - } -] - added
Output schema / properties / bonds / items / properties / ticker / typeAdded value: +[ + "string", + "null" +] - removed
Output schema / properties / issuer_name / anyOfRemoved value: -[ - { - "type": "string" - }, - { - "type": "null" - } -] - added
Output schema / properties / issuer_name / typeAdded value: +[ + "string", + "null" +] - removed
Output schema / properties / next_cursor / anyOfRemoved value: -[ - { - "type": "string" - }, - { - "type": "null" - } -] - added
Output schema / properties / next_cursor / typeAdded value: +[ + "string", + "null" +]
- Changed
company_financial_params_get3 fields changed- removed
Output schema / properties / issuer_name / anyOfRemoved value: -[ - { - "type": "string" - }, - { - "type": "null" - } -] - added
Output schema / properties / issuer_name / typeAdded value: +[ + "string", + "null" +] - changed
Output schema / properties / periods / items / properties / ratios / anyOfPrevious value: -[ - { - "additionalProperties": false, - "properties": { - "capitalization_ratio": { - "anyOf": [ - { - "type": "string" - }, - { - "type": "null" - } - ] - }, - "current_liquidity_ratio": { - "anyOf": [ - { - "type": "string" - }, - { - "type": "null" - } - ] - }, - "financial_independence_ratio": { - "anyOf": [ - { - "type": "string" - }, - { - "type": "null" - } - ] - }, - "financial_leverage_ratio": { - "anyOf": [ - { - "type": "string" - }, - { - "type": "null" - } - ] - }, - "financial_liabilities_ratio": { - "anyOf": [ - { - "type": "string" - }, - { - "type": "null" - } - ] - }, - "financial_stability_ratio": { - "anyOf": [ - { - "type": "string" - }, - { - "type": "null" - } - ] - }, - "own_working_capital_ratio": { - "anyOf": [ - { - "type": "string" - }, - { - "type": "null" - } - ] - } - }, - "required": [ - "current_liquidity_ratio", - "financial_liabilities_ratio", - "financial_independence_ratio", - "own_working_capital_ratio", - "financial_stability_ratio", - "capitalization_ratio", - "financial_leverage_ratio" - ], - "type": "object" - }, - { - "type": "null" - } -]New value: +[ + { + "additionalProperties": false, + "properties": { + "capitalization_ratio": { + "type": [ + "string", + "null" + ] + }, + "current_liquidity_ratio": { + "type": [ + "string", + "null" + ] + }, + "financial_independence_ratio": { + "type": [ + "string", + "null" + ] + }, + "financial_leverage_ratio": { + "type": [ + "string", + "null" + ] + }, + "financial_liabilities_ratio": { + "type": [ + "string", + "null" + ] + }, + "financial_stability_ratio": { + "type": [ + "string", + "null" + ] + }, + "own_working_capital_ratio": { + "type": [ + "string", + "null" + ] + } + }, + "required": [ + "current_liquidity_ratio", + "financial_liabilities_ratio", + "financial_independence_ratio", + "own_working_capital_ratio", + "financial_stability_ratio", + "capitalization_ratio", + "financial_leverage_ratio" + ], + "type": "object" + }, + { + "type": "null" + } +]
- Changed
company_get_by_uuid10 fields changed- removed
Output schema / properties / address / anyOfRemoved value: -[ - { - "type": "string" - }, - { - "type": "null" - } -] - added
Output schema / properties / address / typeAdded value: +[ + "string", + "null" +] - removed
Output schema / properties / full_name / anyOfRemoved value: -[ - { - "type": "string" - }, - { - "type": "null" - } -] - added
Output schema / properties / full_name / typeAdded value: +[ + "string", + "null" +] - removed
Output schema / properties / industry / anyOfRemoved value: -[ - { - "type": "string" - }, - { - "type": "null" - } -] - added
Output schema / properties / industry / typeAdded value: +[ + "string", + "null" +] - removed
Output schema / properties / logo_path / anyOfRemoved value: -[ - { - "type": "string" - }, - { - "type": "null" - } -] - added
Output schema / properties / logo_path / typeAdded value: +[ + "string", + "null" +] - removed
Output schema / properties / unp / anyOfRemoved value: -[ - { - "type": "string" - }, - { - "type": "null" - } -] - added
Output schema / properties / unp / typeAdded value: +[ + "string", + "null" +]
- Changed
company_list12 fields changed- removed
Output schema / properties / companies / items / properties / address / anyOfRemoved value: -[ - { - "type": "string" - }, - { - "type": "null" - } -] - added
Output schema / properties / companies / items / properties / address / typeAdded value: +[ + "string", + "null" +] - removed
Output schema / properties / companies / items / properties / full_name / anyOfRemoved value: -[ - { - "type": "string" - }, - { - "type": "null" - } -] - added
Output schema / properties / companies / items / properties / full_name / typeAdded value: +[ + "string", + "null" +] - removed
Output schema / properties / companies / items / properties / industry / anyOfRemoved value: -[ - { - "type": "string" - }, - { - "type": "null" - } -] - added
Output schema / properties / companies / items / properties / industry / typeAdded value: +[ + "string", + "null" +] - removed
Output schema / properties / companies / items / properties / logo_path / anyOfRemoved value: -[ - { - "type": "string" - }, - { - "type": "null" - } -] - added
Output schema / properties / companies / items / properties / logo_path / typeAdded value: +[ + "string", + "null" +] - removed
Output schema / properties / companies / items / properties / unp / anyOfRemoved value: -[ - { - "type": "string" - }, - { - "type": "null" - } -] - added
Output schema / properties / companies / items / properties / unp / typeAdded value: +[ + "string", + "null" +] - removed
Output schema / properties / next_cursor / anyOfRemoved value: -[ - { - "type": "string" - }, - { - "type": "null" - } -] - added
Output schema / properties / next_cursor / typeAdded value: +[ + "string", + "null" +]
- Changed
company_shares_list14 fields changed- removed
Output schema / properties / issuer_name / anyOfRemoved value: -[ - { - "type": "string" - }, - { - "type": "null" - } -] - added
Output schema / properties / issuer_name / typeAdded value: +[ + "string", + "null" +] - removed
Output schema / properties / next_cursor / anyOfRemoved value: -[ - { - "type": "string" - }, - { - "type": "null" - } -] - added
Output schema / properties / next_cursor / typeAdded value: +[ + "string", + "null" +] - removed
Output schema / properties / shares / items / properties / currency / anyOfRemoved value: -[ - { - "type": "string" - }, - { - "type": "null" - } -] - added
Output schema / properties / shares / items / properties / currency / typeAdded value: +[ + "string", + "null" +] - removed
Output schema / properties / shares / items / properties / is_traded_today / anyOfRemoved value: -[ - { - "type": "boolean" - }, - { - "type": "null" - } -] - added
Output schema / properties / shares / items / properties / is_traded_today / typeAdded value: +[ + "boolean", + "null" +] - removed
Output schema / properties / shares / items / properties / nominal_value / anyOfRemoved value: -[ - { - "type": "string" - }, - { - "type": "null" - } -] - added
Output schema / properties / shares / items / properties / nominal_value / typeAdded value: +[ + "string", + "null" +] - removed
Output schema / properties / shares / items / properties / share_kind / anyOfRemoved value: -[ - { - "type": "string" - }, - { - "type": "null" - } -] - added
Output schema / properties / shares / items / properties / share_kind / typeAdded value: +[ + "string", + "null" +] - removed
Output schema / properties / shares / items / properties / ticker / anyOfRemoved value: -[ - { - "type": "string" - }, - { - "type": "null" - } -] - added
Output schema / properties / shares / items / properties / ticker / typeAdded value: +[ + "string", + "null" +]
- Changed
company_tokens_list12 fields changed- removed
Output schema / properties / issuer_name / anyOfRemoved value: -[ - { - "type": "string" - }, - { - "type": "null" - } -] - added
Output schema / properties / issuer_name / typeAdded value: +[ + "string", + "null" +] - removed
Output schema / properties / next_cursor / anyOfRemoved value: -[ - { - "type": "string" - }, - { - "type": "null" - } -] - added
Output schema / properties / next_cursor / typeAdded value: +[ + "string", + "null" +] - removed
Output schema / properties / tokens / items / properties / percent_rate / anyOfRemoved value: -[ - { - "type": "string" - }, - { - "type": "null" - } -] - added
Output schema / properties / tokens / items / properties / percent_rate / typeAdded value: +[ + "string", + "null" +] - removed
Output schema / properties / tokens / items / properties / sold / anyOfRemoved value: -[ - { - "type": "number" - }, - { - "type": "null" - } -] - added
Output schema / properties / tokens / items / properties / sold / typeAdded value: +[ + "number", + "null" +] - removed
Output schema / properties / tokens / items / properties / token_price / anyOfRemoved value: -[ - { - "type": "string" - }, - { - "type": "null" - } -] - added
Output schema / properties / tokens / items / properties / token_price / typeAdded value: +[ + "string", + "null" +] - removed
Output schema / properties / tokens / items / properties / total_tokens / anyOfRemoved value: -[ - { - "type": "number" - }, - { - "type": "null" - } -] - added
Output schema / properties / tokens / items / properties / total_tokens / typeAdded value: +[ + "number", + "null" +]
- Changed
currency_rate_get5 fields changed- removed
Output schema / properties / date_from / anyOfRemoved value: -[ - { - "type": "string" - }, - { - "type": "null" - } -] - added
Output schema / properties / date_from / typeAdded value: +[ + "string", + "null" +] - removed
Output schema / properties / date_to / anyOfRemoved value: -[ - { - "type": "string" - }, - { - "type": "null" - } -] - added
Output schema / properties / date_to / typeAdded value: +[ + "string", + "null" +] - changed
Output schema / properties / results / items / anyOfPrevious value: -[ - { - "additionalProperties": false, - "properties": { - "currency": { - "enum": [ - "usd", - "eur", - "rub" - ], - "type": "string" - }, - "rate": { - "type": "number" - }, - "rate_date": { - "type": "string" - } - }, - "required": [ - "currency", - "rate_date", - "rate" - ], - "type": "object" - }, - { - "additionalProperties": false, - "properties": { - "avg_rate": { - "type": "number" - }, - "currency": { - "enum": [ - "usd", - "eur", - "rub" - ], - "type": "string" - }, - "data_points": { - "type": "number" - }, - "expected_data_points": { - "type": "number" - }, - "is_complete": { - "type": "boolean" - }, - "max_rate": { - "type": "number" - }, - "min_rate": { - "type": "number" - }, - "period_start": { - "type": "string" - }, - "period_type": { - "enum": [ - "week", - "month" - ], - "type": "string" - }, - "stddev_rate": { - "anyOf": [ - { - "type": "number" - }, - { - "type": "null" - } - ] - } - }, - "required": [ - "currency", - "period_type", - "period_start", - "avg_rate", - "min_rate", - "max_rate", - "stddev_rate", - "data_points", - "expected_data_points", - "is_complete" - ], - "type": "object" - } -]New value: +[ + { + "additionalProperties": false, + "properties": { + "currency": { + "enum": [ + "usd", + "eur", + "rub" + ], + "type": "string" + }, + "rate": { + "type": "number" + }, + "rate_date": { + "type": "string" + } + }, + "required": [ + "currency", + "rate_date", + "rate" + ], + "type": "object" + }, + { + "additionalProperties": false, + "properties": { + "avg_rate": { + "type": "number" + }, + "currency": { + "enum": [ + "usd", + "eur", + "rub" + ], + "type": "string" + }, + "data_points": { + "type": "number" + }, + "expected_data_points": { + "type": "number" + }, + "is_complete": { + "type": "boolean" + }, + "max_rate": { + "type": "number" + }, + "min_rate": { + "type": "number" + }, + "period_start": { + "type": "string" + }, + "period_type": { + "enum": [ + "week", + "month" + ], + "type": "string" + }, + "stddev_rate": { + "type": [ + "number", + "null" + ] + } + }, + "required": [ + "currency", + "period_type", + "period_start", + "avg_rate", + "min_rate", + "max_rate", + "stddev_rate", + "data_points", + "expected_data_points", + "is_complete" + ], + "type": "object" + } +]
- Changed
entity_news_list34 fields changed- removed
Output schema / properties / events / items / properties / article_url / anyOfRemoved value: -[ - { - "type": "string" - }, - { - "type": "null" - } -] - added
Output schema / properties / events / items / properties / article_url / typeAdded value: +[ + "string", + "null" +] - removed
Output schema / properties / events / items / properties / confidence / anyOfRemoved value: -[ - { - "type": "number" - }, - { - "type": "null" - } -] - added
Output schema / properties / events / items / properties / confidence / typeAdded value: +[ + "number", + "null" +] - removed
Output schema / properties / events / items / properties / event_type / anyOfRemoved value: -[ - { - "type": "string" - }, - { - "type": "null" - } -] - added
Output schema / properties / events / items / properties / event_type / typeAdded value: +[ + "string", + "null" +] - removed
Output schema / properties / events / items / properties / impact_type / anyOfRemoved value: -[ - { - "type": "string" - }, - { - "type": "null" - } -] - added
Output schema / properties / events / items / properties / impact_type / typeAdded value: +[ + "string", + "null" +] - removed
Output schema / properties / events / items / properties / links / items / properties / display_name / anyOfRemoved value: -[ - { - "type": "string" - }, - { - "type": "null" - } -] - added
Output schema / properties / events / items / properties / links / items / properties / display_name / typeAdded value: +[ + "string", + "null" +] - removed
Output schema / properties / events / items / properties / links / items / properties / match_confidence / anyOfRemoved value: -[ - { - "type": "number" - }, - { - "type": "null" - } -] - added
Output schema / properties / events / items / properties / links / items / properties / match_confidence / typeAdded value: +[ + "number", + "null" +] - removed
Output schema / properties / events / items / properties / links / items / properties / match_reason / anyOfRemoved value: -[ - { - "type": "string" - }, - { - "type": "null" - } -] - added
Output schema / properties / events / items / properties / links / items / properties / match_reason / typeAdded value: +[ + "string", + "null" +] - removed
Output schema / properties / events / items / properties / links / items / properties / parent_entity_id / anyOfRemoved value: -[ - { - "type": "string" - }, - { - "type": "null" - } -] - added
Output schema / properties / events / items / properties / links / items / properties / parent_entity_id / typeAdded value: +[ + "string", + "null" +] - removed
Output schema / properties / events / items / properties / links / items / properties / source_name / anyOfRemoved value: -[ - { - "type": "string" - }, - { - "type": "null" - } -] - added
Output schema / properties / events / items / properties / links / items / properties / source_name / typeAdded value: +[ + "string", + "null" +] - removed
Output schema / properties / events / items / properties / published_at / anyOfRemoved value: -[ - { - "type": "string" - }, - { - "type": "null" - } -] - added
Output schema / properties / events / items / properties / published_at / typeAdded value: +[ + "string", + "null" +] - removed
Output schema / properties / events / items / properties / source / anyOfRemoved value: -[ - { - "type": "string" - }, - { - "type": "null" - } -] - added
Output schema / properties / events / items / properties / source / typeAdded value: +[ + "string", + "null" +] - removed
Output schema / properties / events / items / properties / summary / anyOfRemoved value: -[ - { - "type": "string" - }, - { - "type": "null" - } -] - added
Output schema / properties / events / items / properties / summary / typeAdded value: +[ + "string", + "null" +] - removed
Output schema / properties / events / items / properties / title / anyOfRemoved value: -[ - { - "type": "string" - }, - { - "type": "null" - } -] - added
Output schema / properties / events / items / properties / title / typeAdded value: +[ + "string", + "null" +] - removed
Output schema / properties / filters / properties / date_from / anyOfRemoved value: -[ - { - "type": "string" - }, - { - "type": "null" - } -] - added
Output schema / properties / filters / properties / date_from / typeAdded value: +[ + "string", + "null" +] - removed
Output schema / properties / filters / properties / date_to / anyOfRemoved value: -[ - { - "type": "string" - }, - { - "type": "null" - } -] - added
Output schema / properties / filters / properties / date_to / typeAdded value: +[ + "string", + "null" +] - removed
Output schema / properties / issuer_name / anyOfRemoved value: -[ - { - "type": "string" - }, - { - "type": "null" - } -] - added
Output schema / properties / issuer_name / typeAdded value: +[ + "string", + "null" +] - removed
Output schema / properties / next_cursor / anyOfRemoved value: -[ - { - "type": "string" - }, - { - "type": "null" - } -] - added
Output schema / properties / next_cursor / typeAdded value: +[ + "string", + "null" +]
- Changed
search_by_name14 fields changed- removed
Output schema / properties / results / items / properties / address / anyOfRemoved value: -[ - { - "type": "string" - }, - { - "type": "null" - } -] - added
Output schema / properties / results / items / properties / address / typeAdded value: +[ + "string", + "null" +] - removed
Output schema / properties / results / items / properties / full_name / anyOfRemoved value: -[ - { - "type": "string" - }, - { - "type": "null" - } -] - added
Output schema / properties / results / items / properties / full_name / typeAdded value: +[ + "string", + "null" +] - removed
Output schema / properties / results / items / properties / industry / anyOfRemoved value: -[ - { - "type": "string" - }, - { - "type": "null" - } -] - added
Output schema / properties / results / items / properties / industry / typeAdded value: +[ + "string", + "null" +] - removed
Output schema / properties / results / items / properties / issuer_code / anyOfRemoved value: -[ - { - "type": "string" - }, - { - "type": "null" - } -] - added
Output schema / properties / results / items / properties / issuer_code / typeAdded value: +[ + "string", + "null" +] - removed
Output schema / properties / results / items / properties / issuer_depository / anyOfRemoved value: -[ - { - "type": "string" - }, - { - "type": "null" - } -] - added
Output schema / properties / results / items / properties / issuer_depository / typeAdded value: +[ + "string", + "null" +] - removed
Output schema / properties / results / items / properties / logo_path / anyOfRemoved value: -[ - { - "type": "string" - }, - { - "type": "null" - } -] - added
Output schema / properties / results / items / properties / logo_path / typeAdded value: +[ + "string", + "null" +] - removed
Output schema / properties / results / items / properties / unp / anyOfRemoved value: -[ - { - "type": "string" - }, - { - "type": "null" - } -] - added
Output schema / properties / results / items / properties / unp / typeAdded value: +[ + "string", + "null" +]
- Changed
search_by_ticker14 fields changed- removed
Output schema / properties / results / items / properties / admission_date / anyOfRemoved value: -[ - { - "type": "string" - }, - { - "type": "null" - } -] - added
Output schema / properties / results / items / properties / admission_date / typeAdded value: +[ + "string", + "null" +] - removed
Output schema / properties / results / items / properties / currency / anyOfRemoved value: -[ - { - "type": "string" - }, - { - "type": "null" - } -] - added
Output schema / properties / results / items / properties / currency / typeAdded value: +[ + "string", + "null" +] - removed
Output schema / properties / results / items / properties / is_trading / anyOfRemoved value: -[ - { - "type": "boolean" - }, - { - "type": "null" - } -] - added
Output schema / properties / results / items / properties / is_trading / typeAdded value: +[ + "boolean", + "null" +] - removed
Output schema / properties / results / items / properties / issuer_name / anyOfRemoved value: -[ - { - "type": "string" - }, - { - "type": "null" - } -] - added
Output schema / properties / results / items / properties / issuer_name / typeAdded value: +[ + "string", + "null" +] - removed
Output schema / properties / results / items / properties / kind / anyOfRemoved value: -[ - { - "type": "string" - }, - { - "type": "null" - } -] - added
Output schema / properties / results / items / properties / kind / typeAdded value: +[ + "string", + "null" +] - removed
Output schema / properties / results / items / properties / nominal_value / anyOfRemoved value: -[ - { - "type": "string" - }, - { - "type": "null" - } -] - added
Output schema / properties / results / items / properties / nominal_value / typeAdded value: +[ + "string", + "null" +] - removed
Output schema / properties / results / items / properties / ticker / anyOfRemoved value: -[ - { - "type": "string" - }, - { - "type": "null" - } -] - added
Output schema / properties / results / items / properties / ticker / typeAdded value: +[ + "string", + "null" +]
- Changed
share_get_by_uuid18 fields changed- removed
Output schema / properties / admission_date / anyOfRemoved value: -[ - { - "type": "string" - }, - { - "type": "null" - } -] - added
Output schema / properties / admission_date / typeAdded value: +[ + "string", + "null" +] - removed
Output schema / properties / currency / anyOfRemoved value: -[ - { - "type": "string" - }, - { - "type": "null" - } -] - added
Output schema / properties / currency / typeAdded value: +[ + "string", + "null" +] - removed
Output schema / properties / is_trading / anyOfRemoved value: -[ - { - "type": "boolean" - }, - { - "type": "null" - } -] - added
Output schema / properties / is_trading / typeAdded value: +[ + "boolean", + "null" +] - removed
Output schema / properties / issuer_name / anyOfRemoved value: -[ - { - "type": "string" - }, - { - "type": "null" - } -] - added
Output schema / properties / issuer_name / typeAdded value: +[ + "string", + "null" +] - removed
Output schema / properties / lot_size / anyOfRemoved value: -[ - { - "type": "number" - }, - { - "type": "null" - } -] - added
Output schema / properties / lot_size / typeAdded value: +[ + "number", + "null" +] - removed
Output schema / properties / name / anyOfRemoved value: -[ - { - "type": "string" - }, - { - "type": "null" - } -] - added
Output schema / properties / name / typeAdded value: +[ + "string", + "null" +] - removed
Output schema / properties / nominal_value / anyOfRemoved value: -[ - { - "type": "string" - }, - { - "type": "null" - } -] - added
Output schema / properties / nominal_value / typeAdded value: +[ + "string", + "null" +] - removed
Output schema / properties / share_kind / anyOfRemoved value: -[ - { - "type": "string" - }, - { - "type": "null" - } -] - added
Output schema / properties / share_kind / typeAdded value: +[ + "string", + "null" +] - removed
Output schema / properties / ticker / anyOfRemoved value: -[ - { - "type": "string" - }, - { - "type": "null" - } -] - added
Output schema / properties / ticker / typeAdded value: +[ + "string", + "null" +]
- Changed
share_list20 fields changed- removed
Output schema / properties / next_cursor / anyOfRemoved value: -[ - { - "type": "string" - }, - { - "type": "null" - } -] - added
Output schema / properties / next_cursor / typeAdded value: +[ + "string", + "null" +] - removed
Output schema / properties / shares / items / properties / admission_date / anyOfRemoved value: -[ - { - "type": "string" - }, - { - "type": "null" - } -] - added
Output schema / properties / shares / items / properties / admission_date / typeAdded value: +[ + "string", + "null" +] - removed
Output schema / properties / shares / items / properties / currency / anyOfRemoved value: -[ - { - "type": "string" - }, - { - "type": "null" - } -] - added
Output schema / properties / shares / items / properties / currency / typeAdded value: +[ + "string", + "null" +] - removed
Output schema / properties / shares / items / properties / is_trading / anyOfRemoved value: -[ - { - "type": "boolean" - }, - { - "type": "null" - } -] - added
Output schema / properties / shares / items / properties / is_trading / typeAdded value: +[ + "boolean", + "null" +] - removed
Output schema / properties / shares / items / properties / issuer_name / anyOfRemoved value: -[ - { - "type": "string" - }, - { - "type": "null" - } -] - added
Output schema / properties / shares / items / properties / issuer_name / typeAdded value: +[ + "string", + "null" +] - removed
Output schema / properties / shares / items / properties / lot_size / anyOfRemoved value: -[ - { - "type": "number" - }, - { - "type": "null" - } -] - added
Output schema / properties / shares / items / properties / lot_size / typeAdded value: +[ + "number", + "null" +] - removed
Output schema / properties / shares / items / properties / name / anyOfRemoved value: -[ - { - "type": "string" - }, - { - "type": "null" - } -] - added
Output schema / properties / shares / items / properties / name / typeAdded value: +[ + "string", + "null" +] - removed
Output schema / properties / shares / items / properties / nominal_value / anyOfRemoved value: -[ - { - "type": "string" - }, - { - "type": "null" - } -] - added
Output schema / properties / shares / items / properties / nominal_value / typeAdded value: +[ + "string", + "null" +] - removed
Output schema / properties / shares / items / properties / share_kind / anyOfRemoved value: -[ - { - "type": "string" - }, - { - "type": "null" - } -] - added
Output schema / properties / shares / items / properties / share_kind / typeAdded value: +[ + "string", + "null" +] - removed
Output schema / properties / shares / items / properties / ticker / anyOfRemoved value: -[ - { - "type": "string" - }, - { - "type": "null" - } -] - added
Output schema / properties / shares / items / properties / ticker / typeAdded value: +[ + "string", + "null" +]
- Changed
share_payouts_get18 fields changed- removed
Output schema / properties / currency / anyOfRemoved value: -[ - { - "type": "string" - }, - { - "type": "null" - } -] - added
Output schema / properties / currency / typeAdded value: +[ + "string", + "null" +] - removed
Output schema / properties / nominal_value / anyOfRemoved value: -[ - { - "type": "string" - }, - { - "type": "null" - } -] - added
Output schema / properties / nominal_value / typeAdded value: +[ + "string", + "null" +] - removed
Output schema / properties / summary / properties / avg_amount_per_share / anyOfRemoved value: -[ - { - "type": "string" - }, - { - "type": "null" - } -] - added
Output schema / properties / summary / properties / avg_amount_per_share / typeAdded value: +[ + "string", + "null" +] - removed
Output schema / properties / summary / properties / dividend_yield_pct / anyOfRemoved value: -[ - { - "type": "number" - }, - { - "type": "null" - } -] - added
Output schema / properties / summary / properties / dividend_yield_pct / typeAdded value: +[ + "number", + "null" +] - removed
Output schema / properties / summary / properties / first_payment_date / anyOfRemoved value: -[ - { - "type": "string" - }, - { - "type": "null" - } -] - added
Output schema / properties / summary / properties / first_payment_date / typeAdded value: +[ + "string", + "null" +] - removed
Output schema / properties / summary / properties / last_payment_date / anyOfRemoved value: -[ - { - "type": "string" - }, - { - "type": "null" - } -] - added
Output schema / properties / summary / properties / last_payment_date / typeAdded value: +[ + "string", + "null" +] - removed
Output schema / properties / summary / properties / max_amount_per_share / anyOfRemoved value: -[ - { - "type": "string" - }, - { - "type": "null" - } -] - added
Output schema / properties / summary / properties / max_amount_per_share / typeAdded value: +[ + "string", + "null" +] - removed
Output schema / properties / summary / properties / min_amount_per_share / anyOfRemoved value: -[ - { - "type": "string" - }, - { - "type": "null" - } -] - added
Output schema / properties / summary / properties / min_amount_per_share / typeAdded value: +[ + "string", + "null" +] - removed
Output schema / properties / ticker / anyOfRemoved value: -[ - { - "type": "string" - }, - { - "type": "null" - } -] - added
Output schema / properties / ticker / typeAdded value: +[ + "string", + "null" +]
- Changed
token_get_by_uuid12 fields changed- removed
Output schema / properties / company_name / anyOfRemoved value: -[ - { - "type": "string" - }, - { - "type": "null" - } -] - added
Output schema / properties / company_name / typeAdded value: +[ + "string", + "null" +] - removed
Output schema / properties / emission_stop / anyOfRemoved value: -[ - { - "type": "string" - }, - { - "type": "null" - } -] - added
Output schema / properties / emission_stop / typeAdded value: +[ + "string", + "null" +] - removed
Output schema / properties / percent_rate / anyOfRemoved value: -[ - { - "type": "string" - }, - { - "type": "null" - } -] - added
Output schema / properties / percent_rate / typeAdded value: +[ + "string", + "null" +] - removed
Output schema / properties / sold / anyOfRemoved value: -[ - { - "type": "number" - }, - { - "type": "null" - } -] - added
Output schema / properties / sold / typeAdded value: +[ + "number", + "null" +] - removed
Output schema / properties / token_price / anyOfRemoved value: -[ - { - "type": "string" - }, - { - "type": "null" - } -] - added
Output schema / properties / token_price / typeAdded value: +[ + "string", + "null" +] - removed
Output schema / properties / total_tokens / anyOfRemoved value: -[ - { - "type": "number" - }, - { - "type": "null" - } -] - added
Output schema / properties / total_tokens / typeAdded value: +[ + "number", + "null" +]
- Changed
token_list14 fields changed- removed
Output schema / properties / next_cursor / anyOfRemoved value: -[ - { - "type": "string" - }, - { - "type": "null" - } -] - added
Output schema / properties / next_cursor / typeAdded value: +[ + "string", + "null" +] - removed
Output schema / properties / tokens / items / properties / company_name / anyOfRemoved value: -[ - { - "type": "string" - }, - { - "type": "null" - } -] - added
Output schema / properties / tokens / items / properties / company_name / typeAdded value: +[ + "string", + "null" +] - removed
Output schema / properties / tokens / items / properties / emission_stop / anyOfRemoved value: -[ - { - "type": "string" - }, - { - "type": "null" - } -] - added
Output schema / properties / tokens / items / properties / emission_stop / typeAdded value: +[ + "string", + "null" +] - removed
Output schema / properties / tokens / items / properties / percent_rate / anyOfRemoved value: -[ - { - "type": "string" - }, - { - "type": "null" - } -] - added
Output schema / properties / tokens / items / properties / percent_rate / typeAdded value: +[ + "string", + "null" +] - removed
Output schema / properties / tokens / items / properties / sold / anyOfRemoved value: -[ - { - "type": "number" - }, - { - "type": "null" - } -] - added
Output schema / properties / tokens / items / properties / sold / typeAdded value: +[ + "number", + "null" +] - removed
Output schema / properties / tokens / items / properties / token_price / anyOfRemoved value: -[ - { - "type": "string" - }, - { - "type": "null" - } -] - added
Output schema / properties / tokens / items / properties / token_price / typeAdded value: +[ + "string", + "null" +] - removed
Output schema / properties / tokens / items / properties / total_tokens / anyOfRemoved value: -[ - { - "type": "number" - }, - { - "type": "null" - } -] - added
Output schema / properties / tokens / items / properties / total_tokens / typeAdded value: +[ + "number", + "null" +]
- Changed
token_trading_stats_get8 fields changed- removed
Output schema / properties / snapshot / properties / percent_rate / anyOfRemoved value: -[ - { - "type": "number" - }, - { - "type": "null" - } -] - added
Output schema / properties / snapshot / properties / percent_rate / typeAdded value: +[ + "number", + "null" +] - removed
Output schema / properties / snapshot / properties / sold_pct / anyOfRemoved value: -[ - { - "type": "number" - }, - { - "type": "null" - } -] - added
Output schema / properties / snapshot / properties / sold_pct / typeAdded value: +[ + "number", + "null" +] - removed
Output schema / properties / snapshot / properties / token_price / anyOfRemoved value: -[ - { - "type": "string" - }, - { - "type": "null" - } -] - added
Output schema / properties / snapshot / properties / token_price / typeAdded value: +[ + "string", + "null" +] - removed
Output schema / properties / totals / properties / avg_tokens_per_active_day / anyOfRemoved value: -[ - { - "type": "number" - }, - { - "type": "null" - } -] - added
Output schema / properties / totals / properties / avg_tokens_per_active_day / typeAdded value: +[ + "number", + "null" +]
- Changed
trading_stats_get38 fields changed- removed
Output schema / properties / daily_series / items / properties / price_max / anyOfRemoved value: -[ - { - "type": "string" - }, - { - "type": "null" - } -] - added
Output schema / properties / daily_series / items / properties / price_max / typeAdded value: +[ + "string", + "null" +] - removed
Output schema / properties / daily_series / items / properties / price_min / anyOfRemoved value: -[ - { - "type": "string" - }, - { - "type": "null" - } -] - added
Output schema / properties / daily_series / items / properties / price_min / typeAdded value: +[ + "string", + "null" +] - removed
Output schema / properties / daily_series / items / properties / price_wavg / anyOfRemoved value: -[ - { - "type": "string" - }, - { - "type": "null" - } -] - added
Output schema / properties / daily_series / items / properties / price_wavg / typeAdded value: +[ + "string", + "null" +] - removed
Output schema / properties / daily_series / items / properties / yield_max / anyOfRemoved value: -[ - { - "type": "string" - }, - { - "type": "null" - } -] - added
Output schema / properties / daily_series / items / properties / yield_max / typeAdded value: +[ + "string", + "null" +] - removed
Output schema / properties / daily_series / items / properties / yield_min / anyOfRemoved value: -[ - { - "type": "string" - }, - { - "type": "null" - } -] - added
Output schema / properties / daily_series / items / properties / yield_min / typeAdded value: +[ + "string", + "null" +] - removed
Output schema / properties / last_trade_date / anyOfRemoved value: -[ - { - "type": "string" - }, - { - "type": "null" - } -] - added
Output schema / properties / last_trade_date / typeAdded value: +[ + "string", + "null" +] - removed
Output schema / properties / price_latest_date / anyOfRemoved value: -[ - { - "type": "string" - }, - { - "type": "null" - } -] - added
Output schema / properties / price_latest_date / typeAdded value: +[ + "string", + "null" +] - removed
Output schema / properties / price_max / anyOfRemoved value: -[ - { - "type": "string" - }, - { - "type": "null" - } -] - added
Output schema / properties / price_max / typeAdded value: +[ + "string", + "null" +] - removed
Output schema / properties / price_min / anyOfRemoved value: -[ - { - "type": "string" - }, - { - "type": "null" - } -] - added
Output schema / properties / price_min / typeAdded value: +[ + "string", + "null" +] - removed
Output schema / properties / price_wavg / anyOfRemoved value: -[ - { - "type": "string" - }, - { - "type": "null" - } -] - added
Output schema / properties / price_wavg / typeAdded value: +[ + "string", + "null" +] - removed
Output schema / properties / price_wavg_latest / anyOfRemoved value: -[ - { - "type": "string" - }, - { - "type": "null" - } -] - added
Output schema / properties / price_wavg_latest / typeAdded value: +[ + "string", + "null" +] - removed
Output schema / properties / ticker / anyOfRemoved value: -[ - { - "type": "string" - }, - { - "type": "null" - } -] - added
Output schema / properties / ticker / typeAdded value: +[ + "string", + "null" +] - removed
Output schema / properties / transactions_count / anyOfRemoved value: -[ - { - "type": "number" - }, - { - "type": "null" - } -] - added
Output schema / properties / transactions_count / typeAdded value: +[ + "number", + "null" +] - removed
Output schema / properties / turnover_amount / anyOfRemoved value: -[ - { - "type": "string" - }, - { - "type": "null" - } -] - added
Output schema / properties / turnover_amount / typeAdded value: +[ + "string", + "null" +] - removed
Output schema / properties / yield_latest_date / anyOfRemoved value: -[ - { - "type": "string" - }, - { - "type": "null" - } -] - added
Output schema / properties / yield_latest_date / typeAdded value: +[ + "string", + "null" +] - removed
Output schema / properties / yield_max / anyOfRemoved value: -[ - { - "type": "string" - }, - { - "type": "null" - } -] - added
Output schema / properties / yield_max / typeAdded value: +[ + "string", + "null" +] - removed
Output schema / properties / yield_min / anyOfRemoved value: -[ - { - "type": "string" - }, - { - "type": "null" - } -] - added
Output schema / properties / yield_min / typeAdded value: +[ + "string", + "null" +] - removed
Output schema / properties / yield_wavg / anyOfRemoved value: -[ - { - "type": "string" - }, - { - "type": "null" - } -] - added
Output schema / properties / yield_wavg / typeAdded value: +[ + "string", + "null" +] - removed
Output schema / properties / yield_wavg_latest / anyOfRemoved value: -[ - { - "type": "string" - }, - { - "type": "null" - } -] - added
Output schema / properties / yield_wavg_latest / typeAdded value: +[ + "string", + "null" +]
5 tool updates
- Changed
bond_get_by_uuid1 field changed- changed
Output schema / properties / percent_rate / anyOfPrevious value: -[ - { - "type": "number" - }, - { - "type": "null" - } -]New value: +[ + { + "type": "string" + }, + { + "type": "null" + } +]
- Changed
bond_list1 field changed- changed
Output schema / properties / bonds / items / properties / percent_rate / anyOfPrevious value: -[ - { - "type": "number" - }, - { - "type": "null" - } -]New value: +[ + { + "type": "string" + }, + { + "type": "null" + } +]
- Changed
company_tokens_list2 fields changed- changed
Output schema / properties / tokens / items / properties / sold / anyOfPrevious value: -[ - { - "type": "string" - }, - { - "type": "null" - } -]New value: +[ + { + "type": "number" + }, + { + "type": "null" + } +] - changed
Output schema / properties / tokens / items / properties / total_tokens / anyOfPrevious value: -[ - { - "type": "string" - }, - { - "type": "null" - } -]New value: +[ + { + "type": "number" + }, + { + "type": "null" + } +]
- Changed
token_get_by_uuid2 fields changed- changed
Output schema / properties / sold / anyOfPrevious value: -[ - { - "type": "string" - }, - { - "type": "null" - } -]New value: +[ + { + "type": "number" + }, + { + "type": "null" + } +] - changed
Output schema / properties / total_tokens / anyOfPrevious value: -[ - { - "type": "string" - }, - { - "type": "null" - } -]New value: +[ + { + "type": "number" + }, + { + "type": "null" + } +]
- Changed
token_list2 fields changed- changed
Output schema / properties / tokens / items / properties / sold / anyOfPrevious value: -[ - { - "type": "string" - }, - { - "type": "null" - } -]New value: +[ + { + "type": "number" + }, + { + "type": "null" + } +] - changed
Output schema / properties / tokens / items / properties / total_tokens / anyOfPrevious value: -[ - { - "type": "string" - }, - { - "type": "null" - } -]New value: +[ + { + "type": "number" + }, + { + "type": "null" + } +]
3 tool updates
- Changed
company_tokens_list4 fields changed- changed
Output schema / properties / tokens / items / properties / percent_rate / anyOfPrevious value: -[ - { - "type": "number" - }, - { - "type": "null" - } -]New value: +[ + { + "type": "string" + }, + { + "type": "null" + } +] - changed
Output schema / properties / tokens / items / properties / sold / anyOfPrevious value: -[ - { - "type": "number" - }, - { - "type": "null" - } -]New value: +[ + { + "type": "string" + }, + { + "type": "null" + } +] - changed
Output schema / properties / tokens / items / properties / token_price / anyOfPrevious value: -[ - { - "type": "number" - }, - { - "type": "null" - } -]New value: +[ + { + "type": "string" + }, + { + "type": "null" + } +] - changed
Output schema / properties / tokens / items / properties / total_tokens / anyOfPrevious value: -[ - { - "type": "number" - }, - { - "type": "null" - } -]New value: +[ + { + "type": "string" + }, + { + "type": "null" + } +]
- Changed
token_get_by_uuid4 fields changed- changed
Output schema / properties / percent_rate / anyOfPrevious value: -[ - { - "type": "number" - }, - { - "type": "null" - } -]New value: +[ + { + "type": "string" + }, + { + "type": "null" + } +] - changed
Output schema / properties / sold / anyOfPrevious value: -[ - { - "type": "number" - }, - { - "type": "null" - } -]New value: +[ + { + "type": "string" + }, + { + "type": "null" + } +] - changed
Output schema / properties / token_price / anyOfPrevious value: -[ - { - "type": "number" - }, - { - "type": "null" - } -]New value: +[ + { + "type": "string" + }, + { + "type": "null" + } +] - changed
Output schema / properties / total_tokens / anyOfPrevious value: -[ - { - "type": "number" - }, - { - "type": "null" - } -]New value: +[ + { + "type": "string" + }, + { + "type": "null" + } +]
- Changed
token_list4 fields changed- changed
Output schema / properties / tokens / items / properties / percent_rate / anyOfPrevious value: -[ - { - "type": "number" - }, - { - "type": "null" - } -]New value: +[ + { + "type": "string" + }, + { + "type": "null" + } +] - changed
Output schema / properties / tokens / items / properties / sold / anyOfPrevious value: -[ - { - "type": "number" - }, - { - "type": "null" - } -]New value: +[ + { + "type": "string" + }, + { + "type": "null" + } +] - changed
Output schema / properties / tokens / items / properties / token_price / anyOfPrevious value: -[ - { - "type": "number" - }, - { - "type": "null" - } -]New value: +[ + { + "type": "string" + }, + { + "type": "null" + } +] - changed
Output schema / properties / tokens / items / properties / total_tokens / anyOfPrevious value: -[ - { - "type": "number" - }, - { - "type": "null" - } -]New value: +[ + { + "type": "string" + }, + { + "type": "null" + } +]
4 tool updates
- Added
company_bonds_list - Added
company_shares_list - Added
company_tokens_list - Added
entity_news_list
15 tool updates
- Changed
bond_get_by_uuid2 fields changed- changed
Input schema / properties / uuid / descriptionPrevious value: -"Bond UUID (8-36 hex characters), usually discovered via search_by_ticker"New 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. Bond id, usually discovered via search_by_ticker." - changed
Output schema / (root)Previous value: -nullNew value: +{ + "$schema": "http://json-schema.org/draft-07/schema#", + "additionalProperties": false, + "properties": { + "admission_date": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + }, + "bond_kind": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + }, + "created_at": { + "type": "string" + }, + "currency": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + }, + "is_active": { + "type": "boolean" + }, + "is_trading": { + "anyOf": [ + { + "type": "boolean" + }, + { + "type": "null" + } + ] + }, + "issuer_name": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + }, + "issuer_uuid": { + "anyOf": [ + { + "description": "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.", + "type": "string" + }, + { + "type": "null" + } + ] + }, + "maturity_date": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + }, + "name": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + }, + "nominal_value": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + }, + "percent_payment_type": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + }, + "percent_rate": { + "anyOf": [ + { + "type": "number" + }, + { + "type": "null" + } + ] + }, + "security_kind": { + "const": "bond", + "type": "string" + }, + "ticker": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + }, + "updated_at": { + "type": "string" + }, + "uuid": { + "description": "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.", + "type": "string" + } + }, + "required": [ + "uuid", + "ticker", + "name", + "issuer_uuid", + "issuer_name", + "security_kind", + "bond_kind", + "nominal_value", + "currency", + "percent_rate", + "percent_payment_type", + "maturity_date", + "is_trading", + "is_active", + "admission_date", + "created_at", + "updated_at" + ], + "type": "object" +}
- Changed
bond_list3 fields changed- changed
Input schema / properties / cursor_uuid / descriptionPrevious value: -"Pagination cursor UUID"New 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. Pagination cursor id from next_cursor before the | delimiter." - changed
Input schema / properties / issuer_uuid / descriptionPrevious value: -"Filter by security_issuer UUID (from search_by_name result with entity_type=\"issuer\")"New 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. Filter by security_issuer id from search_by_name result with entity_type=\"issuer\"." - changed
Output schema / (root)Previous value: -nullNew value: +{ + "$schema": "http://json-schema.org/draft-07/schema#", + "additionalProperties": false, + "properties": { + "bonds": { + "items": { + "additionalProperties": false, + "properties": { + "admission_date": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + }, + "bond_kind": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + }, + "created_at": { + "type": "string" + }, + "currency": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + }, + "is_active": { + "type": "boolean" + }, + "is_trading": { + "anyOf": [ + { + "type": "boolean" + }, + { + "type": "null" + } + ] + }, + "issuer_name": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + }, + "issuer_uuid": { + "anyOf": [ + { + "description": "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.", + "type": "string" + }, + { + "type": "null" + } + ] + }, + "maturity_date": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + }, + "name": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + }, + "nominal_value": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + }, + "percent_payment_type": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + }, + "percent_rate": { + "anyOf": [ + { + "type": "number" + }, + { + "type": "null" + } + ] + }, + "security_kind": { + "const": "bond", + "type": "string" + }, + "ticker": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + }, + "updated_at": { + "type": "string" + }, + "uuid": { + "description": "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.", + "type": "string" + } + }, + "required": [ + "uuid", + "ticker", + "name", + "issuer_uuid", + "issuer_name", + "security_kind", + "bond_kind", + "nominal_value", + "currency", + "percent_rate", + "percent_payment_type", + "maturity_date", + "is_trading", + "is_active", + "admission_date", + "created_at", + "updated_at" + ], + "type": "object" + }, + "type": "array" + }, + "count": { + "type": "number" + }, + "next_cursor": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + } + }, + "required": [ + "bonds", + "count", + "next_cursor" + ], + "type": "object" +}
- Changed
company_financial_params_get2 fields changed- changed
Input schema / properties / uuid / descriptionPrevious value: -"Company or issuer UUID (8-36 hex characters), usually discovered via search_by_name"New 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." - changed
Output schema / (root)Previous value: -nullNew value: +{ + "$schema": "http://json-schema.org/draft-07/schema#", + "additionalProperties": false, + "properties": { + "company_name": { + "type": "string" + }, + "company_uuid": { + "description": "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.", + "type": "string" + }, + "count": { + "type": "number" + }, + "issuer_name": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + }, + "issuer_uuid": { + "anyOf": [ + { + "description": "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.", + "type": "string" + }, + { + "type": "null" + } + ] + }, + "periods": { + "items": { + "additionalProperties": false, + "properties": { + "metrics": { + "additionalProperties": { + "type": "string" + }, + "propertyNames": { + "type": "string" + }, + "type": "object" + }, + "period_date": { + "type": "string" + }, + "ratios": { + "anyOf": [ + { + "additionalProperties": false, + "properties": { + "capitalization_ratio": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + }, + "current_liquidity_ratio": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + }, + "financial_independence_ratio": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + }, + "financial_leverage_ratio": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + }, + "financial_liabilities_ratio": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + }, + "financial_stability_ratio": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + }, + "own_working_capital_ratio": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + } + }, + "required": [ + "current_liquidity_ratio", + "financial_liabilities_ratio", + "financial_independence_ratio", + "own_working_capital_ratio", + "financial_stability_ratio", + "capitalization_ratio", + "financial_leverage_ratio" + ], + "type": "object" + }, + { + "type": "null" + } + ] + } + }, + "required": [ + "period_date", + "metrics", + "ratios" + ], + "type": "object" + }, + "type": "array" + }, + "requested_entity_type": { + "enum": [ + "company", + "issuer" + ], + "type": "string" + }, + "requested_uuid": { + "description": "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.", + "type": "string" + } + }, + "required": [ + "requested_uuid", + "requested_entity_type", + "company_uuid", + "company_name", + "issuer_uuid", + "issuer_name", + "periods", + "count" + ], + "type": "object" +}
- Changed
company_get_by_uuid2 fields changed- changed
Input schema / properties / uuid / descriptionPrevious value: -"Company UUID (8-36 hex characters), usually from search_by_name entity_type=\"company\""New 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 id, usually from search_by_name entity_type=\"company\"." - changed
Output schema / (root)Previous value: -nullNew value: +{ + "$schema": "http://json-schema.org/draft-07/schema#", + "additionalProperties": false, + "properties": { + "address": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + }, + "created_at": { + "type": "string" + }, + "full_name": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + }, + "industry": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + }, + "is_active": { + "type": "boolean" + }, + "logo_path": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + }, + "name": { + "type": "string" + }, + "unp": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + }, + "updated_at": { + "type": "string" + }, + "uuid": { + "description": "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.", + "type": "string" + } + }, + "required": [ + "uuid", + "name", + "full_name", + "unp", + "industry", + "logo_path", + "address", + "is_active", + "created_at", + "updated_at" + ], + "type": "object" +}
- Changed
company_list2 fields changed- changed
Input schema / properties / cursor_uuid / descriptionPrevious value: -"Pagination cursor UUID"New 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. Pagination cursor id from next_cursor before the | delimiter." - changed
Output schema / (root)Previous value: -nullNew value: +{ + "$schema": "http://json-schema.org/draft-07/schema#", + "additionalProperties": false, + "properties": { + "companies": { + "items": { + "additionalProperties": false, + "properties": { + "address": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + }, + "created_at": { + "type": "string" + }, + "full_name": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + }, + "industry": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + }, + "is_active": { + "type": "boolean" + }, + "logo_path": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + }, + "name": { + "type": "string" + }, + "unp": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + }, + "updated_at": { + "type": "string" + }, + "uuid": { + "description": "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.", + "type": "string" + } + }, + "required": [ + "uuid", + "name", + "full_name", + "unp", + "industry", + "logo_path", + "address", + "is_active", + "created_at", + "updated_at" + ], + "type": "object" + }, + "type": "array" + }, + "count": { + "type": "number" + }, + "next_cursor": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + } + }, + "required": [ + "companies", + "count", + "next_cursor" + ], + "type": "object" +}
- Changed
currency_rate_get1 field changed- changed
Output schema / (root)Previous value: -nullNew value: +{ + "$schema": "http://json-schema.org/draft-07/schema#", + "additionalProperties": false, + "properties": { + "base_currency": { + "type": "string" + }, + "count": { + "type": "number" + }, + "currency": { + "items": { + "type": "string" + }, + "type": "array" + }, + "date_from": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + }, + "date_to": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + }, + "group_by": { + "enum": [ + "week", + "month" + ], + "type": "string" + }, + "mode": { + "enum": [ + "latest", + "single_date", + "range", + "grouped" + ], + "type": "string" + }, + "results": { + "items": { + "anyOf": [ + { + "additionalProperties": false, + "properties": { + "currency": { + "enum": [ + "usd", + "eur", + "rub" + ], + "type": "string" + }, + "rate": { + "type": "number" + }, + "rate_date": { + "type": "string" + } + }, + "required": [ + "currency", + "rate_date", + "rate" + ], + "type": "object" + }, + { + "additionalProperties": false, + "properties": { + "avg_rate": { + "type": "number" + }, + "currency": { + "enum": [ + "usd", + "eur", + "rub" + ], + "type": "string" + }, + "data_points": { + "type": "number" + }, + "expected_data_points": { + "type": "number" + }, + "is_complete": { + "type": "boolean" + }, + "max_rate": { + "type": "number" + }, + "min_rate": { + "type": "number" + }, + "period_start": { + "type": "string" + }, + "period_type": { + "enum": [ + "week", + "month" + ], + "type": "string" + }, + "stddev_rate": { + "anyOf": [ + { + "type": "number" + }, + { + "type": "null" + } + ] + } + }, + "required": [ + "currency", + "period_type", + "period_start", + "avg_rate", + "min_rate", + "max_rate", + "stddev_rate", + "data_points", + "expected_data_points", + "is_complete" + ], + "type": "object" + } + ] + }, + "type": "array" + } + }, + "required": [ + "results", + "count", + "mode", + "base_currency", + "currency", + "date_from", + "date_to" + ], + "type": "object" +}
- Changed
search_by_name1 field changed- changed
Output schema / (root)Previous value: -nullNew value: +{ + "$schema": "http://json-schema.org/draft-07/schema#", + "additionalProperties": false, + "properties": { + "count": { + "type": "number" + }, + "query": { + "type": "string" + }, + "results": { + "items": { + "additionalProperties": false, + "properties": { + "address": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + }, + "created_at": { + "type": "string" + }, + "entity_type": { + "enum": [ + "company", + "issuer" + ], + "type": "string" + }, + "full_name": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + }, + "industry": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + }, + "is_active": { + "type": "boolean" + }, + "issuer_code": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + }, + "issuer_depository": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + }, + "linked_company_uuid": { + "anyOf": [ + { + "description": "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.", + "type": "string" + }, + { + "type": "null" + } + ] + }, + "logo_path": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + }, + "name": { + "type": "string" + }, + "unp": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + }, + "updated_at": { + "type": "string" + }, + "uuid": { + "description": "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.", + "type": "string" + } + }, + "required": [ + "entity_type", + "uuid", + "name", + "full_name", + "unp", + "industry", + "logo_path", + "address", + "issuer_code", + "issuer_depository", + "linked_company_uuid", + "is_active", + "created_at", + "updated_at" + ], + "type": "object" + }, + "type": "array" + } + }, + "required": [ + "results", + "count", + "query" + ], + "type": "object" +}
- Changed
search_by_ticker1 field changed- changed
Output schema / (root)Previous value: -nullNew value: +{ + "$schema": "http://json-schema.org/draft-07/schema#", + "additionalProperties": false, + "properties": { + "count": { + "type": "number" + }, + "query": { + "type": "string" + }, + "results": { + "items": { + "additionalProperties": false, + "properties": { + "admission_date": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + }, + "currency": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + }, + "entity_type": { + "enum": [ + "share", + "bond" + ], + "type": "string" + }, + "is_active": { + "type": "boolean" + }, + "is_trading": { + "anyOf": [ + { + "type": "boolean" + }, + { + "type": "null" + } + ] + }, + "issuer_name": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + }, + "issuer_uuid": { + "anyOf": [ + { + "description": "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.", + "type": "string" + }, + { + "type": "null" + } + ] + }, + "kind": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + }, + "nominal_value": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + }, + "ticker": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + }, + "uuid": { + "description": "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.", + "type": "string" + } + }, + "required": [ + "entity_type", + "uuid", + "ticker", + "kind", + "issuer_uuid", + "issuer_name", + "nominal_value", + "currency", + "is_trading", + "is_active", + "admission_date" + ], + "type": "object" + }, + "type": "array" + } + }, + "required": [ + "results", + "count", + "query" + ], + "type": "object" +}
- Changed
share_get_by_uuid2 fields changed- changed
Input schema / properties / uuid / descriptionPrevious value: -"Share UUID (8-36 hex characters), usually discovered via search_by_ticker"New 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. Share id, usually discovered via search_by_ticker." - changed
Output schema / (root)Previous value: -nullNew value: +{ + "$schema": "http://json-schema.org/draft-07/schema#", + "additionalProperties": false, + "properties": { + "admission_date": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + }, + "created_at": { + "type": "string" + }, + "currency": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + }, + "is_active": { + "type": "boolean" + }, + "is_trading": { + "anyOf": [ + { + "type": "boolean" + }, + { + "type": "null" + } + ] + }, + "issuer_name": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + }, + "issuer_uuid": { + "anyOf": [ + { + "description": "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.", + "type": "string" + }, + { + "type": "null" + } + ] + }, + "lot_size": { + "anyOf": [ + { + "type": "number" + }, + { + "type": "null" + } + ] + }, + "name": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + }, + "nominal_value": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + }, + "security_kind": { + "const": "share", + "type": "string" + }, + "share_kind": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + }, + "ticker": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + }, + "updated_at": { + "type": "string" + }, + "uuid": { + "description": "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.", + "type": "string" + } + }, + "required": [ + "uuid", + "ticker", + "name", + "issuer_uuid", + "issuer_name", + "security_kind", + "share_kind", + "nominal_value", + "currency", + "is_trading", + "is_active", + "admission_date", + "lot_size", + "created_at", + "updated_at" + ], + "type": "object" +}
- Changed
share_list3 fields changed- changed
Input schema / properties / cursor_uuid / descriptionPrevious value: -"Pagination cursor UUID"New 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. Pagination cursor id from next_cursor before the | delimiter." - changed
Input schema / properties / issuer_uuid / descriptionPrevious value: -"Filter by security_issuer UUID (from search_by_name result with entity_type=\"issuer\")"New 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. Filter by security_issuer id from search_by_name result with entity_type=\"issuer\"." - changed
Output schema / (root)Previous value: -nullNew value: +{ + "$schema": "http://json-schema.org/draft-07/schema#", + "additionalProperties": false, + "properties": { + "count": { + "type": "number" + }, + "next_cursor": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + }, + "shares": { + "items": { + "additionalProperties": false, + "properties": { + "admission_date": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + }, + "created_at": { + "type": "string" + }, + "currency": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + }, + "is_active": { + "type": "boolean" + }, + "is_trading": { + "anyOf": [ + { + "type": "boolean" + }, + { + "type": "null" + } + ] + }, + "issuer_name": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + }, + "issuer_uuid": { + "anyOf": [ + { + "description": "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.", + "type": "string" + }, + { + "type": "null" + } + ] + }, + "lot_size": { + "anyOf": [ + { + "type": "number" + }, + { + "type": "null" + } + ] + }, + "name": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + }, + "nominal_value": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + }, + "security_kind": { + "const": "share", + "type": "string" + }, + "share_kind": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + }, + "ticker": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + }, + "updated_at": { + "type": "string" + }, + "uuid": { + "description": "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.", + "type": "string" + } + }, + "required": [ + "uuid", + "ticker", + "name", + "issuer_uuid", + "issuer_name", + "security_kind", + "share_kind", + "nominal_value", + "currency", + "is_trading", + "is_active", + "admission_date", + "lot_size", + "created_at", + "updated_at" + ], + "type": "object" + }, + "type": "array" + } + }, + "required": [ + "shares", + "count", + "next_cursor" + ], + "type": "object" +}
- Changed
share_payouts_get2 fields changed- changed
Input schema / properties / uuid / descriptionPrevious value: -"Share UUID (8-36 hex characters), usually discovered via search_by_ticker"New 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. Share id, usually discovered via search_by_ticker." - changed
Output schema / (root)Previous value: -nullNew value: +{ + "$schema": "http://json-schema.org/draft-07/schema#", + "additionalProperties": false, + "properties": { + "currency": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + }, + "events": { + "items": { + "additionalProperties": false, + "properties": { + "amount_per_share": { + "type": "string" + }, + "decision_date": { + "type": "string" + }, + "is_frozen": { + "type": "boolean" + }, + "payment_date": { + "type": "string" + }, + "period_number": { + "type": "number" + }, + "period_type": { + "type": "string" + }, + "period_year": { + "type": "number" + }, + "record_date": { + "type": "string" + }, + "status": { + "type": "string" + }, + "value_source": { + "type": "string" + } + }, + "required": [ + "period_year", + "period_type", + "period_number", + "amount_per_share", + "decision_date", + "record_date", + "payment_date", + "value_source", + "is_frozen", + "status" + ], + "type": "object" + }, + "type": "array" + }, + "nominal_value": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + }, + "share_uuid": { + "description": "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.", + "type": "string" + }, + "summary": { + "additionalProperties": false, + "properties": { + "avg_amount_per_share": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + }, + "cancelled_count": { + "type": "number" + }, + "declared_count": { + "type": "number" + }, + "dividend_yield_pct": { + "anyOf": [ + { + "type": "number" + }, + { + "type": "null" + } + ] + }, + "first_payment_date": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + }, + "last_payment_date": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + }, + "max_amount_per_share": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + }, + "min_amount_per_share": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + }, + "no_dividend_count": { + "type": "number" + }, + "total_amount_per_share": { + "type": "string" + } + }, + "required": [ + "declared_count", + "no_dividend_count", + "cancelled_count", + "total_amount_per_share", + "max_amount_per_share", + "min_amount_per_share", + "avg_amount_per_share", + "last_payment_date", + "first_payment_date", + "dividend_yield_pct" + ], + "type": "object" + }, + "ticker": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + } + }, + "required": [ + "share_uuid", + "ticker", + "currency", + "nominal_value", + "events", + "summary" + ], + "type": "object" +}
- Changed
token_get_by_uuid2 fields changed- changed
Input schema / properties / uuid / descriptionPrevious value: -"Token UUID (8-36 hex characters)"New 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. Token id, usually discovered via token_list." - changed
Output schema / (root)Previous value: -nullNew value: +{ + "$schema": "http://json-schema.org/draft-07/schema#", + "additionalProperties": false, + "properties": { + "company_name": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + }, + "company_uuid": { + "anyOf": [ + { + "description": "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.", + "type": "string" + }, + { + "type": "null" + } + ] + }, + "created_at": { + "type": "string" + }, + "currency": { + "type": "string" + }, + "emission_stop": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + }, + "is_active": { + "type": "boolean" + }, + "name": { + "type": "string" + }, + "percent_rate": { + "anyOf": [ + { + "type": "number" + }, + { + "type": "null" + } + ] + }, + "platform": { + "type": "string" + }, + "sold": { + "anyOf": [ + { + "type": "number" + }, + { + "type": "null" + } + ] + }, + "status": { + "type": "string" + }, + "token_price": { + "anyOf": [ + { + "type": "number" + }, + { + "type": "null" + } + ] + }, + "total_tokens": { + "anyOf": [ + { + "type": "number" + }, + { + "type": "null" + } + ] + }, + "updated_at": { + "type": "string" + }, + "uuid": { + "description": "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.", + "type": "string" + } + }, + "required": [ + "uuid", + "name", + "platform", + "status", + "percent_rate", + "token_price", + "currency", + "total_tokens", + "sold", + "emission_stop", + "company_uuid", + "company_name", + "is_active", + "created_at", + "updated_at" + ], + "type": "object" +}
- Changed
token_list2 fields changed- changed
Input schema / properties / cursor_uuid / descriptionPrevious value: -"Pagination cursor UUID"New 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. Pagination cursor id from next_cursor before the | delimiter." - changed
Output schema / (root)Previous value: -nullNew value: +{ + "$schema": "http://json-schema.org/draft-07/schema#", + "additionalProperties": false, + "properties": { + "count": { + "type": "number" + }, + "next_cursor": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + }, + "tokens": { + "items": { + "additionalProperties": false, + "properties": { + "company_name": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + }, + "company_uuid": { + "anyOf": [ + { + "description": "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.", + "type": "string" + }, + { + "type": "null" + } + ] + }, + "created_at": { + "type": "string" + }, + "currency": { + "type": "string" + }, + "emission_stop": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + }, + "is_active": { + "type": "boolean" + }, + "name": { + "type": "string" + }, + "percent_rate": { + "anyOf": [ + { + "type": "number" + }, + { + "type": "null" + } + ] + }, + "platform": { + "type": "string" + }, + "sold": { + "anyOf": [ + { + "type": "number" + }, + { + "type": "null" + } + ] + }, + "status": { + "type": "string" + }, + "token_price": { + "anyOf": [ + { + "type": "number" + }, + { + "type": "null" + } + ] + }, + "total_tokens": { + "anyOf": [ + { + "type": "number" + }, + { + "type": "null" + } + ] + }, + "updated_at": { + "type": "string" + }, + "uuid": { + "description": "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.", + "type": "string" + } + }, + "required": [ + "uuid", + "name", + "platform", + "status", + "percent_rate", + "token_price", + "currency", + "total_tokens", + "sold", + "emission_stop", + "company_uuid", + "company_name", + "is_active", + "created_at", + "updated_at" + ], + "type": "object" + }, + "type": "array" + } + }, + "required": [ + "tokens", + "count", + "next_cursor" + ], + "type": "object" +}
- Changed
token_trading_stats_get2 fields changed- changed
Input schema / properties / uuid / descriptionPrevious value: -"Token UUID (8-36 hex characters), usually discovered via token_list"New 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. Token id, usually discovered via token_list." - changed
Output schema / (root)Previous value: -nullNew value: +{ + "$schema": "http://json-schema.org/draft-07/schema#", + "additionalProperties": false, + "properties": { + "currency": { + "type": "string" + }, + "daily": { + "items": { + "additionalProperties": false, + "properties": { + "date": { + "type": "string" + }, + "tokens_sold": { + "type": "number" + } + }, + "required": [ + "date", + "tokens_sold" + ], + "type": "object" + }, + "type": "array" + }, + "mode": { + "const": "range", + "type": "string" + }, + "period": { + "additionalProperties": false, + "properties": { + "date_from": { + "type": "string" + }, + "date_to": { + "type": "string" + } + }, + "required": [ + "date_from", + "date_to" + ], + "type": "object" + }, + "platform": { + "type": "string" + }, + "security_kind": { + "const": "token", + "type": "string" + }, + "snapshot": { + "additionalProperties": false, + "properties": { + "percent_rate": { + "anyOf": [ + { + "type": "number" + }, + { + "type": "null" + } + ] + }, + "sold_pct": { + "anyOf": [ + { + "type": "number" + }, + { + "type": "null" + } + ] + }, + "sold_total": { + "type": "number" + }, + "status": { + "type": "string" + }, + "token_price": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + }, + "total_tokens": { + "type": "number" + } + }, + "required": [ + "status", + "token_price", + "percent_rate", + "sold_total", + "total_tokens", + "sold_pct" + ], + "type": "object" + }, + "totals": { + "additionalProperties": false, + "properties": { + "active_days": { + "type": "number" + }, + "avg_tokens_per_active_day": { + "anyOf": [ + { + "type": "number" + }, + { + "type": "null" + } + ] + }, + "tokens_sold": { + "type": "number" + } + }, + "required": [ + "tokens_sold", + "active_days", + "avg_tokens_per_active_day" + ], + "type": "object" + }, + "uuid": { + "description": "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.", + "type": "string" + } + }, + "required": [ + "uuid", + "security_kind", + "platform", + "currency", + "mode", + "period", + "snapshot", + "daily", + "totals" + ], + "type": "object" +}
- Changed
trading_stats_get2 fields changed- changed
Input schema / properties / uuid / descriptionPrevious value: -"Listed share or bond UUID (8-36 hex characters), usually discovered via search_by_ticker"New 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. Listed share or bond id, usually discovered via search_by_ticker." - changed
Output schema / (root)Previous value: -nullNew value: +{ + "$schema": "http://json-schema.org/draft-07/schema#", + "additionalProperties": false, + "properties": { + "daily_series": { + "items": { + "additionalProperties": false, + "properties": { + "price_max": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + }, + "price_min": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + }, + "price_wavg": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + }, + "trade_date": { + "type": "string" + }, + "transactions_count": { + "type": "number" + }, + "turnover_amount": { + "type": "string" + }, + "yield_max": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + }, + "yield_min": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + } + }, + "required": [ + "trade_date", + "price_min", + "price_max", + "price_wavg", + "turnover_amount", + "transactions_count", + "yield_min", + "yield_max" + ], + "type": "object" + }, + "type": "array" + }, + "last_trade_date": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + }, + "mode": { + "enum": [ + "latest_30d", + "range" + ], + "type": "string" + }, + "period": { + "additionalProperties": false, + "properties": { + "date_from": { + "type": "string" + }, + "date_to": { + "type": "string" + } + }, + "required": [ + "date_from", + "date_to" + ], + "type": "object" + }, + "price_latest_date": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + }, + "price_max": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + }, + "price_min": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + }, + "price_wavg": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + }, + "price_wavg_latest": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + }, + "security_kind": { + "enum": [ + "share", + "bond" + ], + "type": "string" + }, + "ticker": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + }, + "trading_days": { + "type": "number" + }, + "transactions_count": { + "anyOf": [ + { + "type": "number" + }, + { + "type": "null" + } + ] + }, + "turnover_amount": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + }, + "uuid": { + "description": "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.", + "type": "string" + }, + "yield_latest_date": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + }, + "yield_max": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + }, + "yield_min": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + }, + "yield_wavg": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + }, + "yield_wavg_latest": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + } + }, + "required": [ + "uuid", + "security_kind", + "ticker", + "mode", + "period", + "last_trade_date", + "trading_days", + "turnover_amount", + "transactions_count", + "price_wavg", + "price_min", + "price_max", + "price_wavg_latest", + "price_latest_date", + "yield_min", + "yield_max", + "yield_wavg", + "yield_wavg_latest", + "yield_latest_date", + "daily_series" + ], + "type": "object" +}
1 tool update
- Added
company_financial_params_get
13 tool updates
- Changed
bond_get_by_uuid1 field changed- changed
Input schema / properties / uuid / descriptionPrevious value: -"Bond UUID (8-36 hex characters)"New value: +"Bond UUID (8-36 hex characters), usually discovered via search_by_ticker"
- Changed
bond_list2 fields changed- changed
Input schema / properties / is_trading / descriptionPrevious value: -"Filter by trading status"New value: +"Filter by is_traded_today flag: true means traded today, not historical liquidity" - changed
Input schema / properties / issuer_uuid / descriptionPrevious value: -"Filter by issuer UUID"New value: +"Filter by security_issuer UUID (from search_by_name result with entity_type=\"issuer\")"
- Changed
company_get_by_uuid1 field changed- changed
Input schema / properties / uuid / descriptionPrevious value: -"Company UUID (8-36 hex characters)"New value: +"Company UUID (8-36 hex characters), usually from search_by_name entity_type=\"company\""
- Changed
company_list1 field changed- changed
Input schema / properties / industry / descriptionPrevious value: -"Filter by industry name"New value: +"Filter by company_industry.name exact value"
- Changed
currency_rate_get3 fields changed- changed
Input schema / properties / currency / descriptionPrevious value: -"Filter to a single currency (usd, eur, or rub). Omit to return all three."New value: +"Filter to one supported foreign currency: usd, eur, or rub. Omit to return all three. BYN is the base currency, not a target." - changed
Input schema / properties / date_from / descriptionPrevious value: -"Range start date in YYYY-MM-DD format (inclusive)."New value: +"Range start date in YYYY-MM-DD format (inclusive). Can be omitted for open-start range." - changed
Input schema / properties / date_to / descriptionPrevious value: -"Range end date in YYYY-MM-DD format (inclusive). Must be >= date_from."New value: +"Range end date in YYYY-MM-DD format (inclusive, >= date_from). Open-ended or today-bounded ranges bypass cache."
- Changed
search_by_name1 field changed- changed
Input schema / properties / query / descriptionPrevious value: -"Name or UNP search query (case-insensitive, e.g. 'bank' matches 'MTBank', 'Priorbank')"New value: +"Company/issuer name or UNP (Belarusian tax ID) search query; case-insensitive, e.g. 'bank' matches 'MTBank', 'Priorbank'"
- Changed
search_by_ticker1 field changed- changed
Input schema / properties / query / descriptionPrevious value: -"Ticker search query (case-insensitive substring, e.g. 'MTB' matches 'MTBank')"New value: +"Ticker search query for listed shares/bonds only (case-insensitive substring, e.g. 'MTB' matches 'MTBank')"
- Changed
share_get_by_uuid1 field changed- changed
Input schema / properties / uuid / descriptionPrevious value: -"Share UUID (8-36 hex characters)"New value: +"Share UUID (8-36 hex characters), usually discovered via search_by_ticker"
- Changed
share_list2 fields changed- changed
Input schema / properties / is_trading / descriptionPrevious value: -"Filter by trading status"New value: +"Filter by is_traded_today flag: true means traded today, not historical liquidity" - changed
Input schema / properties / issuer_uuid / descriptionPrevious value: -"Filter by issuer UUID"New value: +"Filter by security_issuer UUID (from search_by_name result with entity_type=\"issuer\")"
- Added
share_payouts_get - Changed
token_list3 fields changed- changed
Input schema / properties / platform / descriptionPrevious value: -"Filter by platform"New value: +"Filter by tokenization platform: fainex, finstore, bynex, or whitebird." - changed
Input schema / properties / status / descriptionPrevious value: -"Filter by status"New value: +"Filter by token lifecycle status: SELL_NOT_STARTED (sale not open yet), SELL_IN_PROGRESS (currently selling), SELL_SUSPENDED (sale paused), SOLD_OUT (fully sold), SELL_ENDED (sale ended), CIRCULATION_ENDED (matured/circulation ended), OBLIGATIONS_COMPLETED (issuer obligations completed)." - changed
Input schema / properties / status / enumPrevious value: -[ - "ACTIVE", - "SOLD_OUT", - "CLOSED", - "PLANNED", - "SELL_IN_PROGRESS", - "SELL_NOT_STARTED", - "PAUSED" -]New value: +[ + "SELL_NOT_STARTED", + "SELL_IN_PROGRESS", + "SELL_SUSPENDED", + "SOLD_OUT", + "SELL_ENDED", + "CIRCULATION_ENDED", + "OBLIGATIONS_COMPLETED" +]
- Added
token_trading_stats_get - Added
trading_stats_get
1 tool update
- Added
currency_rate_get
10 tool updates
- First observed
bond_get_by_uuid - First observed
bond_list - First observed
company_get_by_uuid - First observed
company_list - First observed
search_by_name - First observed
search_by_ticker - First observed
share_get_by_uuid - First observed
share_list - First observed
token_get_by_uuid - First observed
token_list
Related MCP Connectors
Read-only tokenized stock data: issuers, chains, contract addresses and corporate actions.
Read-only MCP server for The Quiet Protocol's engines, benchmarks, proof, and business data.
Read-only MCP server: verify credentials and browse escrows on the Stellar testnet contract.
Public read-only MCP server for HODLXXI agent identity, trust, receipts, and verification.
Related MCP Servers
- FlicenseNot gradedqualityBmaintenanceRead-only MCP server for Moscow Exchange market data, providing securities search, quotes, candles, trades, and history via the official ISS API.-
- AlicenseAqualityCmaintenanceRead-only MCP server for the Bucharest Stock Exchange, exposing instrument data, OHLCV candles, and fundamentals through a public backend with no authentication.91MIT
- AlicenseAqualityBmaintenanceA read-only MCP server exposing Toss Securities Open API tools for Korean and US stock quotes, symbol search, order books, candles, exchange rates, market calendars, rankings, and market indicators. It does not implement account access or order placement, ensuring no side effects.13MIT
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.