TokenBel Financial Data

company_bonds_list

Read-onlyIdempotent

List a company's active bond summary cards and next_cursor. Accepts a company or linked issuer id. Example: {"uuid":"0d3bf3be","limit":20}.

Input Schema

TableJSON Schema

Name	Required	Description
`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

TableJSON 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

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedSep 25, 2026

changedInput schema / properties / cursor_created_at / description

Previous 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."

changedInput schema / properties / cursor_uuid / description

Previous value: -"TokenBel internal identifier: opaque hexadecimal string, usually 8 characters such as \"78c7e502\"; despite uuid field/tool names, it is not an RFC UUID and normally has no hyphens. 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."

changedInput schema / properties / limit / description

Previous value: -"Max results per page (default 50)."New value: +"Page size; default 50."

changedInput schema / properties / uuid / description

Previous value: -"TokenBel internal identifier: opaque hexadecimal string, usually 8 characters such as \"78c7e502\"; despite uuid field/tool names, it is not an RFC UUID and normally has no hyphens. Company or issuer id, usually discovered via search_by_name."New value: +"TokenBel id (usually 8 hex chars, no hyphens; not an RFC UUID). Company or linked issuer id from search_by_name."

Changed20 schema fields changedSep 11, 2026
- removedOutput schema / properties / bonds / items / properties / bond_kind / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / bonds / items / properties / bond_kind / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / bonds / items / properties / currency / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / bonds / items / properties / currency / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / bonds / items / properties / is_traded_today / anyOf
```
Removed value: -[
-  {
-    "type": "boolean"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / bonds / items / properties / is_traded_today / type
```
Added value: +[
+  "boolean",
+  "null"
+]
```
- removedOutput schema / properties / bonds / items / properties / maturity_date / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / bonds / items / properties / maturity_date / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / bonds / items / properties / nominal_value / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / bonds / items / properties / nominal_value / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / bonds / items / properties / percent_payment_type / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / bonds / items / properties / percent_payment_type / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / bonds / items / properties / percent_rate / anyOf
```
Removed value: -[
-  {
-    "type": "number"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / bonds / items / properties / percent_rate / type
```
Added value: +[
+  "number",
+  "null"
+]
```
- removedOutput schema / properties / bonds / items / properties / ticker / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / bonds / items / properties / ticker / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / issuer_name / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / issuer_name / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / next_cursor / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / next_cursor / type
```
Added value: +[
+  "string",
+  "null"
+]
```
AddedJul 2, 2026

TDQS

A4/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.

All TokenBel Financial Data tools Inspect

Try in Browser

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

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?