TokenBel Financial Data

company_tokens_list

Read-onlyIdempotent

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

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

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

A3.5/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true and idempotentHint=true, so the safety profile is covered. The description adds that the tool resolves the company from either a company or issuer id and that only 'active' tokens are returned, which is genuine behavioral context, but it is thin and overlaps with the uuid schema note.

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

Conciseness4/5

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

Two short sentences, front-loaded with the core action and scope, with the resolution detail second. Efficient, though the second sentence partially duplicates the uuid parameter description.

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

Completeness4/5

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

An output schema exists, so return values need not be described, and annotations cover safety and idempotency. The description is adequate for a paginated read tool, but it omits whether inactive tokens exist and how this differs from the sibling token_list, which an agent selecting among list tools would want.

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

Parameters3/5

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

Schema description coverage is 100%, so the schema already documents all four parameters, including the company-or-issuer nature of uuid and the two-part cursor. The description restates the company/issuer id flexibility but adds no syntax, format, or defaulting detail beyond the schema; baseline 3 applies.

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

Purpose4/5

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

States a specific verb (List) and resource (a company's active tokens/emissions) plus the scope qualifier 'active'. It is clearly different from company_bonds_list and company_shares_list by resource type, but it never explicitly reconciles with the sibling token_list, leaving the token_list vs company_tokens_list relationship to inference.

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

Usage Guidelines3/5

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

The description implies when to use it (you have a company or issuer TokenBel id and want that entity's tokens), and it notes that the id may be a company or an issuer. However, it gives no explicit when-not guidance and never routes the agent to token_list for unfiltered queries or to search_by_name for discovering the id, despite search_by_name being a sibling.

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

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?