TokenBel Financial Data

company_list

Read-onlyIdempotent

Browse active companies by industry; returns companies and next_cursor, not issuer rows. For issuers use search_by_name. Example: {"limit":20}.

Input Schema

TableJSON Schema

Name	Required	Description
`limit`	No	Page size; default 50 (max 1000).
`industry`	No	Exact company industry name.
`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	Default
`count`	Yes
`companies`	Yes
`next_cursor`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedSep 25, 2026

changedInput schema / properties / cursor_created_at / description

Previous value: -"Pagination cursor datetime (ISO 8601)"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. Pagination cursor id from next_cursor before the | delimiter."New value: +"ID before | in next_cursor; pass with cursor_created_at."

changedInput schema / properties / industry / description

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

changedInput schema / properties / limit / description

Previous value: -"Max results (1-1000, default 50)"New value: +"Page size; default 50 (max 1000)."

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.5/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: only active companies are returned, the response includes next_cursor, and issuer rows are excluded. This goes beyond the structured annotations.

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 compact, front-loaded with the core behavior, and every sentence earns its place. The example is brief and illustrative without adding noise.

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 rich schema coverage, output schema, and annotations, the description provides enough context for correct selection and invocation. It covers the active-company scope, pagination signal, and the key alternative tool.

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. The description adds only a minor example ({"limit":20}) and does not meaningfully expand on parameter semantics beyond what the schema provides.

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 uses a specific verb ('browse'), identifies the resource ('active companies'), and clarifies the output shape ('returns companies and next_cursor, not issuer rows'). It also distinguishes itself from search_by_name, making the tool's purpose unambiguous.

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?

It explicitly states when not to use this tool ('not issuer rows') and directs the agent to the alternative ('For issuers use search_by_name'). This gives clear selection guidance without requiring the agent to inspect sibling tools.

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?