TokenBel Financial Data

company_shares_list

Read-onlyIdempotent

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

Changed14 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 / shares / items / properties / currency / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / shares / items / properties / currency / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / shares / items / properties / is_traded_today / anyOf
```
Removed value: -[
-  {
-    "type": "boolean"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / shares / items / properties / is_traded_today / type
```
Added value: +[
+  "boolean",
+  "null"
+]
```
- removedOutput schema / properties / shares / items / properties / nominal_value / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / shares / items / properties / nominal_value / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / shares / items / properties / share_kind / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / shares / items / properties / share_kind / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / shares / items / properties / ticker / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / shares / items / properties / ticker / type
```
Added value: +[
+  "string",
+  "null"
+]
```
AddedJul 2, 2026

TDQS

A4/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 behavioral context beyond annotations: it filters to 'active' shares and explicitly mentions returning a next_cursor, signaling pagination. This enriches the agent's understanding without contradicting 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 a single sentence plus a concrete example, with the core purpose front-loaded. Every word earns its place; there is no fluff or redundant repetition of the tool name. The example is concise and clarifies parameter usage without extra prose.

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?

For a paginated list tool with an output schema, the description covers the essential behavior: it lists active shares and returns a next_cursor. The schema handles cursor mechanics, and annotations cover safety. Missing explicit mention of authorization or rate limits, but those are minor given readOnlyHint. Overall, the description is sufficient for correct invocation.

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% and each parameter is documented (uuid accepts company or linked issuer id, limit defaults to 50, cursor fields for pagination). The description adds an example with uuid and limit, but it repeats what the schema already says about the id type. No additional semantic meaning beyond the schema is provided, so a baseline 3 is appropriate.

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 clearly states a specific action ('List') on a defined resource ('a company's active share summary cards') and explicitly mentions the output includes a next_cursor. This distinguishes it from siblings like share_list (general) and company_tokens_list (different resource) without needing to inspect schemas.

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 (when you need a specific company's shares) but does not explicitly name alternatives or state when not to use it. No mention of when to prefer share_list or how it differs from other company-scoped tools. The 'Accepts a company or linked issuer id' hint is useful but does not replace explicit routing 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?