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 by verifying the domain or GitHub account it belongs to. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
- Status
- Healthy
- Uptime
- 100.0% over 54 days
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-11-25
- URL
TDQS
A3.8/5.0
Scored across 19 tools
Disambiguation4/5
Most tools target distinct resources and actions, with search, get, and list for bonds, shares, tokens, and companies. The only real ambiguity is between issuer-scoped lists (bond_list, share_list) and company-scoped lists (company_bonds_list, company_shares_list), but descriptions clarify the intended input type.
Naming Consistency4/5
Tool names generally follow a consistent snake_case resource_action pattern like bond_get_by_uuid, company_list, and trading_stats_get. Minor deviations exist with search_by_name and search_by_ticker, which put the verb first, but the overall style remains predictable.
Tool Count3/5
With 19 tools, the server sits in the 16-25 range, which feels somewhat heavy. However, the breadth of financial data covered (bonds, shares, tokens, companies, currency, news, statistics) mostly justifies the count, even though a few list tools could potentially be consolidated.
Completeness4/5
The read-only data surface is quite complete: search, list, get, financial parameters, payouts, trading stats, currency rates, and news are all present. Minor gaps exist, such as no dedicated bond payout tool, but agents can typically work around them using the existing get and list tools.
Available Tools
19 toolsbond_get_by_uuidARead-onlyIdempotentInspect
Get a BCSE bond's ticker, issuer, coupon, maturity and trading-today flag. Resolve tickers with search_by_ticker first. Example: {"uuid":"76f01f65"}.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| uuid | Yes | TokenBel id (usually 8 hex chars, no hyphens; not an RFC UUID). Bond id from 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.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 value by specifying the return fields (ticker, issuer, coupon, maturity, trading-today flag), which is behavioral information beyond the annotations. No contradictions with annotations.
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 sentences with no waste. The first sentence states purpose and return fields; the second provides usage hint and an inline example. Information is front-loaded and every sentence contributes.
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?
The tool is a simple get-by-uuid with one parameter and an output schema (though not shown). The description covers what it returns, how to obtain the uuid, and provides an example. For its simplicity, nothing essential is missing; sibling tools are not explicitly referenced but the search_by_ticker hint suffices.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters4/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100% and the schema already provides a detailed description of the uuid (format, source). The description reinforces this with 'Resolve tickers with search_by_ticker first' and provides a concrete example (uuid: 76f01f65), which helps the agent understand the expected value. This exceeds the baseline for high schema coverage.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose5/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the verb 'Get' and the resource 'BCSE bond', listing the exact fields returned (ticker, issuer, coupon, maturity, trading-today flag). This distinguishes it from sibling tools like bond_list (which lists bonds) and company_bonds_list (which lists by company), and it is specific enough for an agent to select it correctly.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines4/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides a clear prerequisite: 'Resolve tickers with search_by_ticker first', which guides the agent on how to obtain the uuid parameter. It implies that this tool is used after search_by_ticker, but does not explicitly contrast with other listing tools. Still, the usage context is clear and actionable.
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 bonds by issuer and trading-today status; returns bonds and next_cursor. Use an issuer row from search_by_name. Example: {"issuer_uuid":"45aca6f7","limit":20}.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Page size; default 50 (max 1000). | |
| is_trading | No | Traded today on BCSE, not historical liquidity. | |
| cursor_uuid | No | ID before | in next_cursor; pass with cursor_created_at. | |
| issuer_uuid | No | TokenBel id (usually 8 hex chars, no hyphens; not an RFC UUID). From search_by_name entity_type='issuer'. | |
| cursor_created_at | No | Timestamp after | in next_cursor; pass with cursor_uuid. |
Output Schema
ParametersJSON Schema
| Name | Required | Description |
|---|---|---|
| bonds | Yes | |
| count | Yes | |
| next_cursor | Yes |
TDQS
A4/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 useful behavioral context: it returns bonds and next_cursor, implying pagination. It does not mention rate limits or other constraints, but given the annotations, this is adequate.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness5/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is two concise sentences plus an example. The core purpose and prerequisite are front-loaded, and there is zero wasted text. The example is illustrative without being verbose.
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?
The tool has an output schema, so return values are covered elsewhere. The description covers pagination via next_cursor, the prerequisite for issuer_uuid, and an example. It could mention the two cursor parameters more explicitly, but the schema and example compensate. Overall, it is fairly complete for a list tool.
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 all five parameters are documented in the schema. The description adds a hint about issuer_uuid (source from search_by_name) and provides an example, but it doesn't elaborate on cursor parameters beyond what the schema says. 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?
The description clearly states the action (list), the resource (active BCSE bonds), and the key filters (issuer and trading-today status). It distinguishes itself from siblings like bond_get_by_uuid (single bond) and company_bonds_list by focusing on issuer-based listing with a specific status filter.
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?
It provides a clear prerequisite: use an issuer row from search_by_name. This tells the agent when to use this tool (when an issuer UUID is known). However, it does not explicitly exclude alternatives like company_bonds_list or mention when not to use it, so it's not a 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_bonds_listARead-onlyIdempotentInspect
List a company's active bond summary cards and next_cursor. Accepts a company or linked issuer id. Example: {"uuid":"0d3bf3be","limit":20}.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| uuid | Yes | TokenBel id (usually 8 hex chars, no hyphens; not an RFC UUID). Company or linked issuer id from search_by_name. | |
| limit | No | Page size; default 50. | |
| cursor_uuid | No | ID before | in next_cursor; pass with cursor_created_at. | |
| cursor_created_at | No | Timestamp after | in next_cursor; pass with cursor_uuid. |
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
A4/5.0
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint and idempotentHint, covering the safety profile. The description adds the 'active' filter and next_cursor pagination, which is useful context, but it does not disclose additional behaviors like error handling or rate limits. Given the annotations carry the primary safety info, a 3 is appropriate.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness5/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single sentence plus an example, with no filler. The purpose is front-loaded, and the example clarifies the expected input format. This is concise and well-structured.
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?
The output schema exists, so return values are defined. The description mentions active bonds and next_cursor, and the schema details all parameters including cursor handling. Annotations cover safety. Everything an agent needs to call the tool correctly is present, though it doesn't explicitly explain the cursor parameter combination beyond 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 the schema already documents all parameters. The description includes an example JSON, which reinforces usage but does not add new semantic meaning beyond the schema. Thus, it meets the baseline for high coverage.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose5/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool lists a company's active bond summary cards and includes pagination via next_cursor. It distinguishes itself from siblings like bond_list (all bonds) and bond_get_by_uuid (single bond) by specifying the company-scoped action.
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?
It provides clear context by stating it accepts a company or linked issuer id, implying when to use it for a company's bonds. However, it does not explicitly mention alternative tools or conditions when not to use it, so it falls short of the highest bar.
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 a company's financial statement metrics and ratios, newest periods first. Accepts a company or linked issuer id from search_by_name. Example: {"uuid":"311ff09f","limit_periods":4}.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| uuid | Yes | TokenBel id (usually 8 hex chars, no hyphens; not an RFC UUID). Company or linked issuer id from search_by_name. | |
| limit_periods | No | Newest periods to return; default 8 (max 100). |
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.1/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, covering the safety profile. The description adds useful behavioral context beyond that: results are returned newest-period-first, and the accepted id can be a company or a linked issuer id. This is helpful but not extensive.
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 compact sentences plus an example carry all necessary information with no filler. The core purpose is front-loaded, and the example is illustrative without repeating schema details.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness5/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the small parameter set, complete schema coverage, full annotations, and an existing output schema, the description covers everything needed to select and invoke the tool correctly. It even notes the ordering behavior and id provenance, which are not visible in structured fields.
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 fully documents both uuid and limit_periods. The description adds a working example and reinforces the id source, but does not meaningfully extend parameter semantics beyond the schema.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose5/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description states a specific verb ('Get'), a concrete resource ('a company's financial statement metrics and ratios'), and a behavioral detail ('newest periods first'). This clearly distinguishes it from sibling tools like company_get_by_uuid, which would fetch general company data, and company_list, which lists companies.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines4/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides clear context for when to call it: whenever financial metrics/ratios are needed for a company, using an id from search_by_name. It does not explicitly name alternatives or exclusions, but the context is sufficient to guide selection among the large sibling set.
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 company catalogue row, including name, UNP, industry and activity flag; includes inactive companies. Find company IDs with search_by_name. Example: {"uuid":"730f9a9e"}.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| uuid | Yes | TokenBel id (usually 8 hex chars, no hyphens; not an RFC UUID). 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
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already provide readOnlyHint and idempotentHint, covering the safety profile. The description adds useful behavioral context by noting that inactive companies are included and listing the catalogue fields returned, but it does not go deeply beyond that; the output schema covers return-value details.
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 plus a concrete example; every part earns its place. The main scope is front-loaded, and the workflow pointer to search_by_name follows naturally without unnecessary detail.
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 a single required parameter, a fully described schema, a present output schema, and read-only/idempotent annotations, the tool is easy to invoke correctly. The description supplies the only missing context: how to obtain the uuid and that inactive companies are intentionally included.
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?
The schema already documents uuid as a TokenBel id, its usual format (8 hex chars, no hyphens), and its source from search_by_name. The added example '{"uuid":"730f9a9e"}' reinforces the format but does not add substantially new semantics, so the schema-heavy baseline of 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?
The description states a specific verb and resource ('Get a company catalogue row') and enumerates the returned fields (name, UNP, industry, activity flag), plus the key scope detail that inactive companies are included. This clearly distinguishes it from sibling tools like company_list and the other get_by_uuid tools.
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?
It gives a clear usage context by directing the agent to find company IDs via search_by_name, which is the necessary prerequisite for the uuid parameter. It does not explicitly say when to use company_list instead, but the by-uuid lookup intent is unambiguous.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
company_listARead-onlyIdempotentInspect
Browse active companies by industry; returns companies and next_cursor, not issuer rows. For issuers use search_by_name. Example: {"limit":20}.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Page size; default 50 (max 1000). | |
| industry | No | Exact company industry name. | |
| cursor_uuid | No | ID before | in next_cursor; pass with cursor_created_at. | |
| cursor_created_at | No | Timestamp after | in next_cursor; pass with cursor_uuid. |
Output Schema
ParametersJSON Schema
| Name | Required | Description |
|---|---|---|
| count | Yes | |
| companies | Yes | |
| next_cursor | 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 the safety profile is covered. The description adds useful behavioral context: only active companies are returned, the response includes next_cursor, and issuer rows are excluded. This goes beyond the structured annotations.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness5/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is compact, front-loaded with the core behavior, and every sentence earns its place. The example is brief and illustrative without adding noise.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness5/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the rich schema coverage, output schema, and annotations, the description provides enough context for correct selection and invocation. It covers the active-company scope, pagination signal, and the key alternative tool.
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. The description adds only a minor example ({"limit":20}) and does not meaningfully expand on parameter semantics beyond what the schema provides.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose5/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description uses a specific verb ('browse'), identifies the resource ('active companies'), and clarifies the output shape ('returns companies and next_cursor, not issuer rows'). It also distinguishes itself from search_by_name, making the tool's purpose unambiguous.
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?
It explicitly states when not to use this tool ('not issuer rows') and directs the agent to the alternative ('For issuers use search_by_name'). This gives clear selection guidance without requiring the agent to inspect sibling tools.
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 a company's active token summary cards and next_cursor. Accepts a company or linked issuer id. Example: {"uuid":"7b860c81","limit":20}.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| uuid | Yes | TokenBel id (usually 8 hex chars, no hyphens; not an RFC UUID). Company or linked issuer id from search_by_name. | |
| limit | No | Page size; default 50. | |
| cursor_uuid | No | ID before | in next_cursor; pass with cursor_created_at. | |
| cursor_created_at | No | Timestamp after | in next_cursor; pass with cursor_uuid. |
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
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 useful behavioral context beyond those annotations by specifying that it returns 'active token summary cards' and includes a 'next_cursor' for pagination, and by clarifying that it accepts either a company or linked issuer id.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness5/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is short, purposeful, and front-loaded with the core action and resource. Every sentence contributes: the list action, the accepted id type, and a concrete JSON example. There is no fluff, repetition, or unnecessary detail.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness5/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the read-only and idempotent annotations, a 4-parameter paginated list tool, and a full output schema, the description plus schema provide everything needed to call the tool correctly. The pagination parameters are explained in the schema, and the description adds the key domain-specific context about active summary cards and acceptable id types.
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 description coverage is 100%, so the baseline is 3. The description adds value beyond the schema through a concrete example, '{"uuid":"7b860c81","limit":20}', and by restating the key acceptance rule that the uuid can be a company or linked issuer id. The cursor-related parameters are sufficiently documented in the schema itself.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose5/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description opens with a specific verb and resource: 'List a company's active token summary cards and next_cursor.' It clearly identifies the domain (company tokens) and distinguishes itself from sibling tools like company_bonds_list, company_shares_list, and token_list by emphasizing company-level, active token summary cards.
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 usage context by focusing on company tokens and mentioning that it accepts a company or linked issuer id. However, it does not explicitly state when to prefer this tool over alternatives such as token_list, nor does it provide any when-not-to-use guidance.
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 FX rates in BYN per 1 USD/EUR/RUB. No dates = latest; date = one day; date_from/date_to = range; group_by + both bounds = weekly/monthly averages. Example: {"currency":"usd","date":"2026-06-18"}.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| date | No | YYYY-MM-DD; cannot combine with range dates or group_by. | |
| date_to | No | Inclusive range end (YYYY-MM-DD); must be >= date_from. | |
| currency | No | Foreign currency; omit for all three. BYN is the base. | |
| group_by | No | Week/month average; requires both range dates. | |
| date_from | No | Inclusive range start (YYYY-MM-DD); optional for open start. |
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.4/5.0
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint and idempotentHint, covering the safety profile. The description adds valuable behavioral context by explaining how different date parameters alter the response (single day vs. range vs. averaged series), plus a concrete example. It does not mention error handling or response format, but the output schema covers returns.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness5/5
Is the description appropriately sized, front-loaded, and free of redundancy?
Three sentences, zero filler. The core purpose is front-loaded, the mode rules are compressed into one clear sentence, and the example is immediately useful. Every word earns its place.
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 simple read-only FX getter with rich schema descriptions, annotations, and an output schema, the description covers the key decision points: what the tool returns, all parameter modes, and a sample invocation. Minor omissions like date inclusivity or holiday handling are either in the schema or non-critical for correct use.
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 each parameter is already documented. The description goes beyond the schema by explaining the interactions between parameters (e.g., group_by requires both range bounds, no dates means latest) and provides an example. This adds meaningful semantic value without repeating schema text.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose5/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description states a specific verb ('Get'), a resource ('NBRB FX rates in BYN per 1 USD/EUR/RUB'), and differentiates from siblings by focusing on currency rates, which none of the sibling tools cover. The three exchange currencies and base currency are explicitly identified.
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 clearly explains when to use each parameter combination: no dates for latest, date for one day, range dates for a range, and group_by for weekly/monthly averages. It does not name alternatives, but the sibling list makes it obvious this is the only FX-rate tool, so explicit routing is unnecessary.
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 published news across a company/issuer and linked securities; returns events with links, tags and next_cursor. Filter by event/impact type or date. Example: {"uuid":"f2c03989","impact_types":["negative"]}.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| uuid | Yes | TokenBel id (usually 8 hex chars, no hyphens; not an RFC UUID). Company or issuer id from search_by_name. | |
| limit | No | Page size; default 20 (max 50). | |
| date_to | No | Inclusive event date end (YYYY-MM-DD). | |
| date_from | No | Inclusive event date start (YYYY-MM-DD). | |
| event_types | No | Types (case-insensitive): company_news, share_event, bond_event, token_event, emission_event, corporate_action, payment_event, default_risk, financial_report, regulatory_update, tax_update, market_infrastructure, deposit_event, precious_metal_event, currency_market_event, market_data, other. | |
| impact_types | No | Impact types: positive, neutral, negative, mixed; case-insensitive. | |
| cursor_event_id | No | Numeric event ID before | in next_cursor; pass with cursor_published_at. | |
| cursor_published_at | No | Sort timestamp after | in next_cursor; pass with cursor_event_id. |
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=true and idempotentHint=true. The description adds further behavioral context: it returns events with links, tags and next_cursor, supports filtering by event/impact type or date, and implies no side effects. This goes beyond the annotation-only safety profile, though it doesn't describe cursor-handling edge cases or error behavior.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness5/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is compact and effective: a purpose sentence, a return/filter sentence, and one concrete example. It is front-loaded with the most important information and contains no redundant restatement of schema fields.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness5/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the rich input schema, output schema, and read-only annotations, the description is complete enough for an agent to call the tool correctly. It explains the broad behavior, mentions pagination via next_cursor, describes available filter dimensions, and provides an example; the remaining details are covered by the structured schema.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters3/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, so the schema already documents all parameters in detail, including uuid format, limit behavior, date formats, enum-like allowed values, and cursor pairing. The description adds only a high-level filter summary and a compact JSON example, which is helpful but not substantial additional semantic meaning.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose5/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description opens with a clear verb and resource: 'List published news across a company/issuer and linked securities.' It also specifies the return content ('events with links, tags and next_cursor'), making the tool's purpose unmistakable and easily distinguished from the sibling market-data and search tools.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines3/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description clearly implies when to use the tool: when an agent needs published news for a company/issuer and its linked securitiescars. However, it does not explicitly state when to prefer it over alternatives or when not to use it, and it relies on the schema to mention that the uuid comes from search_by_name.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
search_by_nameARead-onlyIdempotentInspect
Find companies and securities issuers by name or UNP; results tag entity_type. Use company uuid for company_get_by_uuid, issuer uuid for share_list/bond_list; linked_company_uuid joins them when known. Example: {"query":"Агрофинанс"}.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Result cap; default 20 (max 100). | |
| query | Yes | Case-insensitive company/issuer name or Belarusian UNP. |
Output Schema
ParametersJSON Schema
| Name | Required | Description |
|---|---|---|
| count | Yes | |
| query | Yes | |
| results | Yes |
TDQS
A4/5.0
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true and idempotentHint=true, covering the safety profile. The description adds meaningful behavior beyond annotations: results tag entity_type, and linked_company_uuid joins company and issuer records when known. This gives the agent clear expectations about result structure without contradicting the annotations.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness5/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is three short, efficient sentences. The main action is front-loaded, followed by routing guidance and a concrete example. There is no filler or repetition of schema 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?
Given the output schema exists and annotations cover idempotence and read-only behavior, the description provides all critical context: the search purpose, an example, and how to use results with downstream tools. The only minor gap is not referencing search_by_ticker as the ticker-based alternative, but this does not prevent correct invocation.
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?
Both parameters (query, limit) already have full descriptions in the input schema, so schema coverage is 100%. The description adds a concrete example query but no additional semantic detail beyond the schema. This matches the baseline 3 for high schema coverage.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose5/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states a specific action and resource: 'Find companies and securities issuers by name or UNP'. The explicit mention of name/UNP differentiates it from the sibling search_by_ticker, which searches by ticker. The additional detail about entity_type tagging further clarifies the tool's output.
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 provides valuable post-search routing instructions—which uuid to use for company_get_by_uuid, share_list, bond_list, and how linked_company_uuid connects them. However, it never explicitly states when to choose this tool over alternatives like search_by_ticker, so usage context is implied rather than spelled out.
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
Find BCSE shares/bonds by ticker substring; returns entity_type and TokenBel uuid for detail or trading tools. Tokens have no tickers. Example: {"query":"ASB"}.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Result cap; default 20 (max 100). | |
| query | Yes | Case-insensitive share/bond ticker substring. |
Output Schema
ParametersJSON Schema
| Name | Required | Description |
|---|---|---|
| count | Yes | |
| query | Yes | |
| results | 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 safe read-only nature is covered. The description adds value beyond annotations by disclosing substring matching behavior, stating what the result supplies (entity_type and TokenBel uuid), and clarifying the token limitation. This is useful behavioral context without redundancy.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness5/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is compact and front-loaded: the action and scope appear in the first sentence, followed by output purpose, a key exclusion, and a concrete example. Every sentence adds useful information with 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 simple lookup tool with fully documented parameters, read-only annotations, and an output schema, the description provides all necessary context: what it searches, what it returns, how to use the result, and an important domain limitation. No essential information is missing for correct invocation.
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 both query and limit are already documented in the schema. The description reinforces 'ticker substring' and provides an example query, but it does not materially expand parameter meaning beyond what the schema already states. A 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?
The description opens with a specific verb and resource: 'Find BCSE shares/bonds by ticker substring.' It also distinguishes itself from search_by_name by specifying the lookup key (ticker rather than name) and from token tools by noting 'Tokens have no tickers.' This makes the tool's purpose immediately identifiable.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines4/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides clear usage context: it is for locating shares/bonds by ticker substring and returning UUIDs for downstream detail or trading tools. It also states an exclusion ('Tokens have no tickers') that prevents misuse. It does not explicitly name search_by_name as the alternative for name-based lookup, but the context is strong enough to guide selection.
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 token's platform, sale status, price, rate and issuer. Tokens have no tickers; find the id with token_list. Example: {"uuid":"78c7e502"}.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| uuid | Yes | TokenBel id (usually 8 hex chars, no hyphens; not an RFC UUID). Token id from 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.9/5.0
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint and idempotentHint, and the description's 'Get' wording is consistent with those. The description adds a small scoping note about token ids and tickers, but no additional behavioral details such as return format or side effects. With annotations covering safety, this is adequate.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness5/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is three short, purposeful sentences: the first front-loads the operation, the second explains the prerequisite, and the third gives a concrete example. There is no filler or redundant restatement.
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 one-parameter read-only getter with an output schema, the description is complete enough: it lists the returned fields, explains how to obtain the necessary uuid, and gives an example. The output schema covers return details, and annotations cover the safety profile.
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%: the schema already explains that uuid is a TokenBel id, usually 8 hex chars, not an RFC UUID, and sourced from token_list. The description's example reinforces this but adds little beyond the schema, 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?
The description states a specific verb and resource: 'Get a token's platform, sale status, price, rate and issuer.' It also clarifies that tokens have no tickers and that the id comes from token_list, which helps distinguish this tool from ticker-based search siblings.
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 provides implied workflow guidance: tokens have no tickers, so the agent should find the id with token_list before calling this tool. However, it does not explicitly state when to prefer this over token_trading_stats_get or other sibling getters.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
token_listBRead-onlyIdempotentInspect
Browse active tokenized securities by platform or sale status; returns tokens and next_cursor. Tokens have no tickers. Example: {"platform":"finstore","limit":20}.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Page size; default 50 (max 1000). | |
| status | No | Sale/circulation state; SELL_IN_PROGRESS is on sale, SOLD_OUT is fully sold, OBLIGATIONS_COMPLETED is repaid. | |
| platform | No | Tokenization platform. | |
| cursor_uuid | No | ID before | in next_cursor; pass with cursor_created_at. | |
| cursor_created_at | No | Timestamp after | in next_cursor; pass with cursor_uuid. |
Output Schema
ParametersJSON Schema
| Name | Required | Description |
|---|---|---|
| count | Yes | |
| tokens | Yes | |
| next_cursor | Yes |
TDQS
B3.3/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 description does not need to restate safety. It adds a pagination signal (next_cursor) and a domain caveat (no tickers), but does not describe ordering, default behavior, or operational constraints. This is adequate but not rich.
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 compact sentences plus a concrete example with no filler. The core intent, result shape, and a critical domain caveat are front-loaded. This is near-ideal concision.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness3/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The output schema covers return shape and the input schema covers parameters, so the description only needs to add selection guidance and caveats. It gives an example and a no-tickers note, but 'active' is ambiguous against statuses like SELL_ENDED, and it does not clarify list-vs-get use cases. Overall it is minimally complete.
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 defines all five parameters including enums and cursor semantics. The example with platform and limit reinforces usage but adds no semantic content 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.
Purpose4/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description states a specific verb (Browse) and resource (tokenized securities), and notes it returns tokens and next_cursor. The 'Tokens have no tickers' hint is useful, but no sibling is named, so differentiation from other list/get tools is implicit rather than explicit.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines2/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance is provided about when to use token_list instead of token_get_by_uuid, bond_list, share_list, or company_tokens_list. The only implicit hint is that tokens have no tickers, which cautions against ticker-based lookup but does not define selection criteria. This is a clear gap for a list tool with many listing siblings.
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 a token's primary-market tokens-sold daily series, totals and snapshot; not secondary trading. No dates = last 30 days; either date bound is allowed. Find the id with token_list. Example: {"uuid":"78c7e502"}.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| uuid | Yes | TokenBel id (usually 8 hex chars, no hyphens; not an RFC UUID). Token id from token_list. | |
| date_to | No | Inclusive YYYY-MM-DD end (>= start); defaults to today. | |
| date_from | No | Inclusive YYYY-MM-DD start; defaults to 30 days before end. |
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 the safety profile is covered. The description adds meaningful behavioral context: the output is a daily series plus totals and snapshot, the scope is primary-market only, and date bounds are optional with specific defaults. This enriches the agent's understanding beyond the annotations.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness5/5
Is the description appropriately sized, front-loaded, and free of redundancy?
Three short sentences with no filler. The primary purpose and exclusion are front-loaded, followed by default behavior and prerequisite lookup. The one-line JSON example is compact and earns its place.
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, idempotent tool with an output schema, the description covers everything an agent needs to select and call it: scope, exclusions, defaults, id source, and example. No missing pieces that would cause incorrect invocation.
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. The description adds value by clarifying that uuid comes from token_list, that no dates means the last 30 days, and that either date bound alone is acceptable. The example JSON reinforces parameter usage.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose5/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description opens with a specific verb and resource: 'Get a token's primary-market tokens-sold daily series, totals and snapshot'. It immediately distinguishes itself from siblings by stating 'not secondary trading', which disambiguates it from trading_stats_get and related market tools. This is a clear, specific purpose statement.
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?
It explicitly tells the agent when not to use it ('not secondary trading') and how to find the required id ('Find the id with token_list'). It also explains default date behavior and that either date bound is allowed. It stops short of naming the alternative tool (e.g., trading_stats_get) outright, but the exclusion is clear enough.
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 share/bond trading totals and daily_series. No dates = latest 30 days; both dates = range (yield_wavg and *_latest are null). Find the id with search_by_ticker. Example: {"uuid":"a97f1fed","date_from":"2026-06-01","date_to":"2026-06-30"}.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| uuid | Yes | TokenBel id (usually 8 hex chars, no hyphens; not an RFC UUID). Share/bond id from search_by_ticker. | |
| date_to | No | Inclusive YYYY-MM-DD end (>= start); supply both dates or neither. | |
| date_from | No | Inclusive YYYY-MM-DD start; supply both dates or neither. |
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.7/5.0
Behavior5/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already indicate read-only and idempotent behavior, and the description adds valuable non-obvious semantics: default date window, null behavior for yield_wavg and *_latest when dates are supplied, and UUID format expectations. This exceeds what annotations alone convey.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness5/5
Is the description appropriately sized, front-loaded, and free of redundancy?
Three sentences pack all essential information: function, default behavior, null caveat, lookup prerequisite, and an example. No filler; the most important facts are front-loaded and the example is compressed but instructive.
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 need not explain return values. It covers id acquisition, date semantics, defaults, and edge-case nulls, making it complete for correct invocation. The sibling context is adequately handled by naming the share/bond scope.
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 descriptions cover 100% of parameters and already explain inclusive dates and the both-or-neither rule. The description adds the default 30-day behavior, clarifies null outcomes, and gives a concrete JSON example, thereby enriching parameter understanding beyond the schema.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose5/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description states a specific verb ('Get'), a specific resource ('share/bond trading totals and daily_series'), and clearly distinguishes from sibling token_trading_stats_get by limiting scope to shares/bonds. It also contrasts with generic lookup tools like share_get_by_uuid by naming the trading-specific output.
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 gives clear usage context: no dates means default 30 days, both dates means range, and it instructs finding the id via search_by_ticker. It does not explicitly state when not to use this tool or name alternatives, but the conditions are concrete enough to guide selection.
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_uuid1 field changed- changed
Input schema / properties / uuid / descriptionPrevious 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."New value: +"TokenBel id (usually 8 hex chars, no hyphens; not an RFC UUID). Bond id from search_by_ticker."
- Changed
bond_list5 fields changed- changed
Input schema / properties / cursor_created_at / descriptionPrevious value: -"Pagination cursor datetime (ISO 8601)"New value: +"Timestamp after | in next_cursor; pass with cursor_uuid." - changed
Input schema / properties / cursor_uuid / descriptionPrevious 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."New value: +"ID before | in next_cursor; pass with cursor_created_at." - changed
Input schema / properties / is_trading / descriptionPrevious value: -"Filter by is_traded_today flag: true means traded today, not historical liquidity"New value: +"Traded today on BCSE, not historical liquidity." - changed
Input schema / properties / issuer_uuid / descriptionPrevious 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\"."New value: +"TokenBel id (usually 8 hex chars, no hyphens; not an RFC UUID). From search_by_name entity_type='issuer'." - changed
Input schema / properties / limit / descriptionPrevious value: -"Max results (1-1000, default 50)"New value: +"Page size; default 50 (max 1000)."
- Changed
company_bonds_list4 fields changed- changed
Input schema / properties / cursor_created_at / descriptionPrevious value: -"Opaque cursor datetime part (ISO 8601) from the next_cursor returned by a prior call; pass both cursor parts together."New value: +"Timestamp after | in next_cursor; pass with cursor_uuid." - changed
Input schema / properties / cursor_uuid / descriptionPrevious 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. Opaque cursor id part from the next_cursor returned by a prior call; pass both cursor parts together."New value: +"ID before | in next_cursor; pass with cursor_created_at." - changed
Input schema / properties / limit / descriptionPrevious value: -"Max results per page (default 50)."New value: +"Page size; default 50." - changed
Input schema / properties / uuid / descriptionPrevious value: -"TokenBel internal identifier: opaque hexadecimal string, usually 8 characters such as \"78c7e502\"; despite uuid field/tool names, it is not an RFC UUID and normally has no hyphens. Company or issuer id, usually discovered via search_by_name."New value: +"TokenBel id (usually 8 hex chars, no hyphens; not an RFC UUID). Company or linked issuer id from search_by_name."
- Changed
company_financial_params_get2 fields changed- changed
Input schema / properties / limit_periods / descriptionPrevious value: -"Max number of periods to return (newest first). Default 8."New value: +"Newest periods to return; default 8 (max 100)." - changed
Input schema / properties / uuid / descriptionPrevious value: -"TokenBel internal identifier: opaque hexadecimal string, usually 8 characters such as \"78c7e502\"; despite uuid field/tool names, it is not an RFC UUID and normally has no hyphens. Company or issuer id, usually discovered via search_by_name."New value: +"TokenBel id (usually 8 hex chars, no hyphens; not an RFC UUID). Company or linked issuer id from search_by_name."
- Changed
company_get_by_uuid1 field changed- changed
Input schema / properties / uuid / descriptionPrevious 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\"."New value: +"TokenBel id (usually 8 hex chars, no hyphens; not an RFC UUID). From search_by_name entity_type='company'."
- Changed
company_list4 fields changed- changed
Input schema / properties / cursor_created_at / descriptionPrevious value: -"Pagination cursor datetime (ISO 8601)"New value: +"Timestamp after | in next_cursor; pass with cursor_uuid." - changed
Input schema / properties / cursor_uuid / descriptionPrevious 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."New value: +"ID before | in next_cursor; pass with cursor_created_at." - changed
Input schema / properties / industry / descriptionPrevious value: -"Filter by company_industry.name exact value"New value: +"Exact company industry name." - changed
Input schema / properties / limit / descriptionPrevious value: -"Max results (1-1000, default 50)"New value: +"Page size; default 50 (max 1000)."
- Changed
company_shares_list4 fields changed- changed
Input schema / properties / cursor_created_at / descriptionPrevious value: -"Opaque cursor datetime part (ISO 8601) from the next_cursor returned by a prior call; pass both cursor parts together."New value: +"Timestamp after | in next_cursor; pass with cursor_uuid." - changed
Input schema / properties / cursor_uuid / descriptionPrevious 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. Opaque cursor id part from the next_cursor returned by a prior call; pass both cursor parts together."New value: +"ID before | in next_cursor; pass with cursor_created_at." - changed
Input schema / properties / limit / descriptionPrevious value: -"Max results per page (default 50)."New value: +"Page size; default 50." - changed
Input schema / properties / uuid / descriptionPrevious value: -"TokenBel internal identifier: opaque hexadecimal string, usually 8 characters such as \"78c7e502\"; despite uuid field/tool names, it is not an RFC UUID and normally has no hyphens. Company or issuer id, usually discovered via search_by_name."New value: +"TokenBel id (usually 8 hex chars, no hyphens; not an RFC UUID). Company or linked issuer id from search_by_name."
- Changed
company_tokens_list4 fields changed- changed
Input schema / properties / cursor_created_at / descriptionPrevious value: -"Opaque cursor datetime part (ISO 8601) from the next_cursor returned by a prior call; pass both cursor parts together."New value: +"Timestamp after | in next_cursor; pass with cursor_uuid." - changed
Input schema / properties / cursor_uuid / descriptionPrevious 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. Opaque cursor id part from the next_cursor returned by a prior call; pass both cursor parts together."New value: +"ID before | in next_cursor; pass with cursor_created_at." - changed
Input schema / properties / limit / descriptionPrevious value: -"Max results per page (default 50)."New value: +"Page size; default 50." - changed
Input schema / properties / uuid / descriptionPrevious value: -"TokenBel internal identifier: opaque hexadecimal string, usually 8 characters such as \"78c7e502\"; despite uuid field/tool names, it is not an RFC UUID and normally has no hyphens. Company or issuer id, usually discovered via search_by_name."New value: +"TokenBel id (usually 8 hex chars, no hyphens; not an RFC UUID). Company or linked issuer id from search_by_name."
- Changed
currency_rate_get5 fields changed- changed
Input schema / properties / currency / descriptionPrevious value: -"Filter to one supported foreign currency: usd, eur, or rub. Omit to return all three. BYN is the base currency, not a target."New value: +"Foreign currency; omit for all three. BYN is the base." - changed
Input schema / properties / date / descriptionPrevious value: -"Single date in YYYY-MM-DD format. Mutually exclusive with date_from/date_to."New value: +"YYYY-MM-DD; cannot combine with range dates or group_by." - changed
Input schema / properties / date_from / descriptionPrevious value: -"Range start date in YYYY-MM-DD format (inclusive). Can be omitted for open-start range."New value: +"Inclusive range start (YYYY-MM-DD); optional for open start." - changed
Input schema / properties / date_to / descriptionPrevious value: -"Range end date in YYYY-MM-DD format (inclusive, >= date_from). Open-ended or today-bounded ranges bypass cache."New value: +"Inclusive range end (YYYY-MM-DD); must be >= date_from." - changed
Input schema / properties / group_by / descriptionPrevious value: -"Aggregate by week or month. Requires a date range (date_from/date_to), not a single date."New value: +"Week/month average; requires both range dates."
- Changed
entity_news_list8 fields changed- changed
Input schema / properties / cursor_event_id / descriptionPrevious value: -"Opaque pagination cursor part 1 (the last event id) from the next_cursor returned by a prior call; pass both cursor parts together."New value: +"Numeric event ID before | in next_cursor; pass with cursor_published_at." - changed
Input schema / properties / cursor_published_at / descriptionPrevious value: -"Opaque pagination cursor part 2 (the last event sort-key timestamp) from the next_cursor returned by a prior call; pass both cursor parts together."New value: +"Sort timestamp after | in next_cursor; pass with cursor_event_id." - changed
Input schema / properties / date_from / descriptionPrevious value: -"Optional inclusive lower bound on the event date (ISO YYYY-MM-DD)."New value: +"Inclusive event date start (YYYY-MM-DD)." - changed
Input schema / properties / date_to / descriptionPrevious value: -"Optional inclusive upper bound on the event date (ISO YYYY-MM-DD)."New value: +"Inclusive event date end (YYYY-MM-DD)." - changed
Input schema / properties / event_types / descriptionPrevious value: -"Optional filter on news_event.event_type. Valid values: company_news, share_event, bond_event, token_event, emission_event, corporate_action, payment_event, default_risk, financial_report, regulatory_update, tax_update, market_infrastructure, deposit_event, precious_metal_event, currency_market_event, market_data, other. Case-insensitive."New value: +"Types (case-insensitive): company_news, share_event, bond_event, token_event, emission_event, corporate_action, payment_event, default_risk, financial_report, regulatory_update, tax_update, market_infrastructure, deposit_event, precious_metal_event, currency_market_event, market_data, other." - changed
Input schema / properties / impact_types / descriptionPrevious value: -"Optional filter on news_event.impact_type. Valid values: positive, neutral, negative, mixed. Case-insensitive."New value: +"Impact types: positive, neutral, negative, mixed; case-insensitive." - changed
Input schema / properties / limit / descriptionPrevious value: -"Max results per page (default 20, max 50)."New value: +"Page size; default 20 (max 50)." - changed
Input schema / properties / uuid / descriptionPrevious value: -"TokenBel internal identifier: opaque hexadecimal string, usually 8 characters such as \"78c7e502\"; despite uuid field/tool names, it is not an RFC UUID and normally has no hyphens. Company or issuer id, usually discovered via search_by_name."New value: +"TokenBel id (usually 8 hex chars, no hyphens; not an RFC UUID). Company or issuer id from search_by_name."
- Changed
search_by_name2 fields changed- changed
Input schema / properties / limit / descriptionPrevious value: -"Max results (1-100, default 20)"New value: +"Result cap; default 20 (max 100)." - changed
Input schema / properties / query / descriptionPrevious value: -"Company/issuer name or UNP (Belarusian tax ID) search query; case-insensitive, e.g. 'bank' matches 'MTBank', 'Priorbank'"New value: +"Case-insensitive company/issuer name or Belarusian UNP."
- Changed
search_by_ticker2 fields changed- changed
Input schema / properties / limit / descriptionPrevious value: -"Max results (1-100, default 20)"New value: +"Result cap; default 20 (max 100)." - changed
Input schema / properties / query / descriptionPrevious value: -"Ticker search query for listed shares/bonds only (case-insensitive substring, e.g. 'MTB' matches 'MTBank')"New value: +"Case-insensitive share/bond ticker substring."
- Changed
share_get_by_uuid1 field changed- changed
Input schema / properties / uuid / descriptionPrevious 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."New value: +"TokenBel id (usually 8 hex chars, no hyphens; not an RFC UUID). Share id from search_by_ticker."
- Changed
share_list5 fields changed- changed
Input schema / properties / cursor_created_at / descriptionPrevious value: -"Pagination cursor datetime (ISO 8601)"New value: +"Timestamp after | in next_cursor; pass with cursor_uuid." - changed
Input schema / properties / cursor_uuid / descriptionPrevious 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."New value: +"ID before | in next_cursor; pass with cursor_created_at." - changed
Input schema / properties / is_trading / descriptionPrevious value: -"Filter by is_traded_today flag: true means traded today, not historical liquidity"New value: +"Traded today on BCSE, not historical liquidity." - changed
Input schema / properties / issuer_uuid / descriptionPrevious 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\"."New value: +"TokenBel id (usually 8 hex chars, no hyphens; not an RFC UUID). From search_by_name entity_type='issuer'." - changed
Input schema / properties / limit / descriptionPrevious value: -"Max results (1-1000, default 50)"New value: +"Page size; default 50 (max 1000)."
- Changed
share_payouts_get1 field changed- changed
Input schema / properties / uuid / descriptionPrevious 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."New value: +"TokenBel id (usually 8 hex chars, no hyphens; not an RFC UUID). Share id from search_by_ticker."
- Changed
token_get_by_uuid1 field changed- changed
Input schema / properties / uuid / descriptionPrevious 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."New value: +"TokenBel id (usually 8 hex chars, no hyphens; not an RFC UUID). Token id from token_list."
- Changed
token_list5 fields changed- changed
Input schema / properties / cursor_created_at / descriptionPrevious value: -"Pagination cursor datetime (ISO 8601)"New value: +"Timestamp after | in next_cursor; pass with cursor_uuid." - changed
Input schema / properties / cursor_uuid / descriptionPrevious 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."New value: +"ID before | in next_cursor; pass with cursor_created_at." - changed
Input schema / properties / limit / descriptionPrevious value: -"Max results (1-1000, default 50)"New value: +"Page size; default 50 (max 1000)." - changed
Input schema / properties / platform / descriptionPrevious value: -"Filter by tokenization platform: fainex, finstore, bynex, or whitebird."New value: +"Tokenization platform." - changed
Input schema / properties / status / descriptionPrevious 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)."New value: +"Sale/circulation state; SELL_IN_PROGRESS is on sale, SOLD_OUT is fully sold, OBLIGATIONS_COMPLETED is repaid."
- Changed
token_trading_stats_get3 fields changed- changed
Input schema / properties / date_from / descriptionPrevious value: -"Range start date YYYY-MM-DD (inclusive). Defaults to date_to minus 30 days when omitted."New value: +"Inclusive YYYY-MM-DD start; defaults to 30 days before end." - changed
Input schema / properties / date_to / descriptionPrevious value: -"Range end date YYYY-MM-DD (inclusive, >= date_from). Defaults to today when omitted."New value: +"Inclusive YYYY-MM-DD end (>= start); defaults to today." - changed
Input schema / properties / uuid / descriptionPrevious 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."New value: +"TokenBel id (usually 8 hex chars, no hyphens; not an RFC UUID). Token id from token_list."
- Changed
trading_stats_get3 fields changed- changed
Input schema / properties / date_from / descriptionPrevious value: -"Range start date YYYY-MM-DD (inclusive). Provide both date_from and date_to for range mode; omit both for latest_30d mode."New value: +"Inclusive YYYY-MM-DD start; supply both dates or neither." - changed
Input schema / properties / date_to / descriptionPrevious value: -"Range end date YYYY-MM-DD (inclusive, >= date_from). Provide both date_from and date_to for range mode; ranges ending today bypass cache."New value: +"Inclusive YYYY-MM-DD end (>= start); supply both dates or neither." - changed
Input schema / properties / uuid / descriptionPrevious 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."New value: +"TokenBel id (usually 8 hex chars, no hyphens; not an RFC UUID). Share/bond id from search_by_ticker."
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.
- FensoryOAuthcom.fensory
Trading MCP server for AI agents, with live market data, account reads and controlled execution.
Read-only educational MCP for CryptoDecentral Sovereign. No auth, trading, custody, or advice.
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.-
- AlicenseAqualityAmaintenanceRead-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.