TokenBel Financial Data

company_shares_list

Read-onlyIdempotent

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

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

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

A3.7/5.0

Behavior3/5

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

Annotations already declare readOnlyHint and idempotentHint, so safety is covered. The description adds genuinely useful behavior beyond that: the id is resolved to a company and the tool then returns that company's shares, and the payload consists of 'summary cards' (implying a lighter projection). It does not discuss pagination behavior or the meaning of 'active'.

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?

Two sentences, no filler, with the core action and the dual-id affordance front-loaded. Nothing can be trimmed without losing information.

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?

An output schema exists, so return-value details need not be restated. For a read-only, idempotent, well-schematized list tool, the description supplies the one non-obvious fact (dual id acceptance) plus the resolution behavior, which is sufficient.

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 are already documented, including that uuid is a company or issuer id and the two-part cursor convention. The description's 'company OR issuer' note duplicates what the schema already states, adding no new parameter meaning — baseline 3 is appropriate.

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?

The description names a specific verb and resource ('List summary cards of a company's active shares'), and the 'active shares' scope is a real qualifier. It does not name any sibling (e.g. share_list for all shares or share_get_by_uuid), so the agent must infer differentiation from context rather than from the text.

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?

It gives one actionable usage fact — that the id may be a company OR an issuer id — which tells the agent it need not resolve first. However, there is no explicit when-to-use guidance versus share_list, company_tokens_list, or how to obtain the id via search_by_name (which is only mentioned in the schema).

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?