TokenBel Financial Data

company_bonds_list

Read-onlyIdempotent

List summary cards of a company's active bonds. Accepts a company OR issuer TokenBel id; resolves the company and returns its bonds.

Input Schema

TableJSON Schema

Name	Required	Description
`uuid`	Yes	TokenBel internal identifier: opaque hexadecimal string, usually 8 characters such as "78c7e502"; despite uuid field/tool names, it is not an RFC UUID and normally has no hyphens. Company or issuer id, usually discovered via search_by_name.
`limit`	No	Max results per page (default 50).
`cursor_uuid`	No	TokenBel internal identifier: opaque hexadecimal string, usually 8 characters such as "78c7e502"; despite uuid field/tool names, it is not an RFC UUID and normally has no hyphens. Opaque cursor id part from the next_cursor returned by a prior call; pass both cursor parts together.
`cursor_created_at`	No	Opaque cursor datetime part (ISO 8601) from the next_cursor returned by a prior call; pass both cursor parts together.

Output Schema

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.

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

A3.6/5.0

Behavior3/5

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

Annotations already declare readOnlyHint and idempotentHint, so the safety profile is covered. The description adds genuinely useful behavior beyond that: an issuer id is accepted and resolved into a company before returning bonds. It does not mention pagination behavior despite the cursor parameters, leaving a gap.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences with no waste; the primary action is front-loaded and the id-resolution caveat follows immediately. Every clause carries information an agent needs.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return values need not be explained, and the schema documents all four parameters including pagination. The description covers purpose and the company/issuer id resolution, leaving only minor gaps such as paging expectations.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the schema already fully documents uuid, limit, and both cursor parts. The description's note that uuid may be a company OR issuer id largely restates the schema's 'Company or issuer id' text, adding little new meaning, so baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('List summary cards of a company's active bonds'), and narrows scope to active bonds for a single company, which implicitly separates it from the broader bond_list. It does not name a sibling explicitly, so it stays at 4 rather than 5.

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

Usage Guidelines3/5

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

The second sentence signals the trigger condition (you have a company OR issuer id) and notes the id is resolved to a company, which implies when to use it. However, it never states when to prefer this over bond_list or bond_get_by_uuid, nor any exclusion, so guidance is only implied.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

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?