TokenBel Financial Data

company_list

Read-onlyIdempotent

List active company catalogue rows with optional filtering by industry. This does not list security_issuer rows directly; use search_by_name to find issuers and then share_list/bond_list with issuer_uuid. Supports cursor-based pagination.

Input Schema

TableJSON Schema

Name	Required	Description
`limit`	No	Max results (1-1000, default 50)
`industry`	No	Filter by company_industry.name exact value
`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
`companies`	Yes
`next_cursor`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed12 schema fields changedSep 11, 2026
- removedOutput schema / properties / companies / items / properties / address / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / companies / items / properties / address / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / companies / items / properties / full_name / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / companies / items / properties / full_name / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / companies / items / properties / industry / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / companies / items / properties / industry / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / companies / items / properties / logo_path / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / companies / items / properties / logo_path / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / companies / items / properties / unp / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / companies / items / properties / unp / 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"
+]
```

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": {
+    "companies": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "address": {
+            "anyOf": [
+              {
+                "type": "string"
+              },
+              {
+                "type": "null"
+              }
+            ]
+          },
+          "created_at": {
+            "type": "string"
+          },
+          "full_name": {
+            "anyOf": [
+              {
+                "type": "string"
+              },
+              {
+                "type": "null"
+              }
+            ]
+          },
+          "industry": {
+            "anyOf": [
+              {
+                "type": "string"
+              },
+              {
+                "type": "null"
+              }
+            ]
+          },
+          "is_active": {
+            "type": "boolean"
+          },
+          "logo_path": {
+            "anyOf": [
+              {
+                "type": "string"
+              },
+              {
+                "type": "null"
+              }
+            ]
+          },
+          "name": {
+            "type": "string"
+          },
+          "unp": {
+            "anyOf": [
+              {
+                "type": "string"
+              },
+              {
+                "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",
+          "full_name",
+          "unp",
+          "industry",
+          "logo_path",
+          "address",
+          "is_active",
+          "created_at",
+          "updated_at"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "count": {
+      "type": "number"
+    },
+    "next_cursor": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    }
+  },
+  "required": [
+    "companies",
+    "count",
+    "next_cursor"
+  ],
+  "type": "object"
+}

Changed1 schema field changedJun 25, 2026

changedInput schema / properties / industry / description

Previous value: -"Filter by industry name"New value: +"Filter by company_industry.name exact value"

First observedJun 9, 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 the pagination behavior ('cursor-based') and the scope limitation regarding issuer rows. It does not discuss rate limits, ordering guarantees, or result-count behavior, but with annotations and an output schema present the remaining burden is light.

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 short sentences, front-loaded with the primary purpose before the exclusion and pagination notes. Slightly more text is spent on the issuer redirection than strictly needed, but every clause carries information.

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 schema, output schema, and annotations, the description supplies everything an agent needs to select and invoke it: scope, the negative scope, the alternative path, and pagination. Only minor details (default page size, ordering) are absent, and those are visible in 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 all four parameters (limit, industry, cursor_uuid, cursor_created_at) are already documented in the schema, including the non-obvious uuid-format caveat for cursor_uuid. The description only restates the industry filter, adding no new parameter semantics — the baseline 3 applies.

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 company catalogue rows') plus an optional filter, and explicitly names what it is not ('does not list security_issuer rows directly'). An agent can distinguish it from share_list/bond_list/search_by_name without opening any schema.

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

Usage Guidelines5/5

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

Gives an explicit routing rule for the issuer case: use search_by_name first, then share_list/bond_list with issuer_uuid. That is a concrete when-to-use-this-vs-alternative instruction rather than an implied one.

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?