TokenBel Financial Data

token_list

Read-onlyIdempotent

List active tokens with optional filtering by fintech platform and token lifecycle status. Tokens do not have tickers; use this list tool to browse tokenized securities by platform/status. Supports cursor-based pagination.

Input Schema

TableJSON Schema

Name	Required	Description
`limit`	No	Max results (1-1000, default 50)
`status`	No	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).
`platform`	No	Filter by tokenization platform: fainex, finstore, bynex, or whitebird.
`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. Pagination cursor id from next_cursor before the \| delimiter.
`cursor_created_at`	No	Pagination cursor datetime (ISO 8601)

Output Schema

TableJSON Schema

Name	Required	Description	Default
`count`	Yes
`tokens`	Yes
`next_cursor`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed14 schema fields changedSep 11, 2026
- 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 / company_name / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / tokens / items / properties / company_name / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / tokens / items / properties / emission_stop / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / tokens / items / properties / emission_stop / 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"
+  }
+]

Changed2 schema fields changedJun 26, 2026

changedInput schema / properties / cursor_uuid / description

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

changedOutput 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"
+}

Changed3 schema fields changedJun 25, 2026

changedInput schema / properties / platform / description

Previous value: -"Filter by platform"New value: +"Filter by tokenization platform: fainex, finstore, bynex, or whitebird."

changedInput schema / properties / status / description

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

changedInput schema / properties / status / enum

Previous 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"
+]

First observedJun 9, 2026

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, so the safety profile is covered by structured data. The description adds cursor-based pagination behavior, which is genuinely beyond the annotations, but the qualifier 'active tokens' sits awkwardly against the status enum that includes terminal states (SELL_ENDED, CIRCULATION_ENDED), leaving the returned scope slightly ambiguous.

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?

Three compact sentences, front-loaded with the purpose and filtering capability, then the ticker caveat, then pagination. Efficient overall, though the pagination sentence is a slightly detached tack-on rather than integrated into the browsing guidance.

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?

With a full output schema, rich annotations, and 100%-documented parameters, the description only needs to frame purpose and scoping, which it does. The one remaining gap is the meaning of 'active' given the terminal status values offered as filters.

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%: limit, status (with per-value explanations), platform, and both cursor fields are fully documented in the schema itself. The description adds no parameter-level syntax, defaults, or interplay (e.g., how the two cursor fields pair), so this is the baseline 3 case where structured data does the lifting.

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?

States a specific verb and resource ('List active tokens') plus the two filter axes (platform, lifecycle status), and explicitly notes that tokens lack tickers, distinguishing this tool from the ticker-driven search_by_ticker/share_list/bond_list siblings. An agent can identify this as the browse-tokenized-securities entry point without opening a schema.

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?

Gives clear usage context: use this list tool to browse tokenized securities by platform/status, implicitly steering agents away from ticker-based lookups. However it never names an explicit alternative (e.g., token_get_by_uuid for a single token, company_tokens_list for company-scoped results) or states when not to use it, so exclusion guidance is absent.

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?