TokenBel Financial Data

company_tokens_list

Read-onlyIdempotent

List a company's active token summary cards and next_cursor. Accepts a company or linked issuer id. Example: {"uuid":"7b860c81","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
`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

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

Changed12 schema fields changedSep 11, 2026
- 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"
+]
```
- removedOutput schema / properties / tokens / items / properties / percent_rate / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / tokens / items / properties / percent_rate / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / tokens / items / properties / sold / anyOf
```
Removed value: -[
-  {
-    "type": "number"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / tokens / items / properties / sold / type
```
Added value: +[
+  "number",
+  "null"
+]
```
- removedOutput schema / properties / tokens / items / properties / token_price / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / tokens / items / properties / token_price / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / tokens / items / properties / total_tokens / anyOf
```
Removed value: -[
-  {
-    "type": "number"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / tokens / items / properties / total_tokens / type
```
Added value: +[
+  "number",
+  "null"
+]
```

Changed2 schema fields changedJul 3, 2026

changedOutput schema / properties / tokens / items / properties / sold / anyOf

Previous value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "type": "number"
+  },
+  {
+    "type": "null"
+  }
+]

changedOutput schema / properties / tokens / items / properties / total_tokens / anyOf

Previous value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "type": "number"
+  },
+  {
+    "type": "null"
+  }
+]

Changed4 schema fields changedJul 2, 2026

changedOutput schema / properties / tokens / items / properties / percent_rate / anyOf

Previous value: -[
-  {
-    "type": "number"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

changedOutput schema / properties / tokens / items / properties / sold / anyOf

Previous value: -[
-  {
-    "type": "number"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

changedOutput schema / properties / tokens / items / properties / token_price / anyOf

Previous value: -[
-  {
-    "type": "number"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

changedOutput schema / properties / tokens / items / properties / total_tokens / anyOf

Previous value: -[
-  {
-    "type": "number"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

AddedJul 2, 2026

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.

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?