TokenBel Financial Data

share_get_by_uuid

Read-onlyIdempotent

Get a single BCSE exchange-listed share by its TokenBel internal identifier (field name: uuid). Returns ticker, issuer_uuid/issuer_name, share_kind (common/preferred), nominal value, lot size, and is_trading (traded today, not historical liquidity). Use search_by_ticker first when starting from a ticker.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`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. Share id, usually discovered via search_by_ticker.

Output Schema

TableJSON Schema

Name	Required	Description
`name`	Yes
`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.
`ticker`	Yes
`currency`	Yes
`lot_size`	Yes
`is_active`	Yes
`created_at`	Yes
`is_trading`	Yes
`share_kind`	Yes
`updated_at`	Yes
`issuer_name`	Yes
`issuer_uuid`	Yes
`nominal_value`	Yes
`security_kind`	Yes
`admission_date`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed18 schema fields changedSep 11, 2026

removedOutput schema / properties / admission_date / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

addedOutput schema / properties / admission_date / type
```
Added value: +[
+  "string",
+  "null"
+]
```

removedOutput schema / properties / currency / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

addedOutput schema / properties / currency / type
```
Added value: +[
+  "string",
+  "null"
+]
```

removedOutput schema / properties / is_trading / anyOf

Removed value: -[
-  {
-    "type": "boolean"
-  },
-  {
-    "type": "null"
-  }
-]

addedOutput schema / properties / is_trading / type
```
Added value: +[
+  "boolean",
+  "null"
+]
```

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 / lot_size / anyOf

Removed value: -[
-  {
-    "type": "number"
-  },
-  {
-    "type": "null"
-  }
-]

addedOutput schema / properties / lot_size / type
```
Added value: +[
+  "number",
+  "null"
+]
```

removedOutput schema / properties / name / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

addedOutput schema / properties / name / type
```
Added value: +[
+  "string",
+  "null"
+]
```

removedOutput schema / properties / nominal_value / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

addedOutput schema / properties / nominal_value / type
```
Added value: +[
+  "string",
+  "null"
+]
```

removedOutput schema / properties / share_kind / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

addedOutput schema / properties / share_kind / type
```
Added value: +[
+  "string",
+  "null"
+]
```

removedOutput schema / properties / ticker / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

addedOutput schema / properties / ticker / type
```
Added value: +[
+  "string",
+  "null"
+]
```

Changed2 schema fields changedJun 26, 2026

changedInput schema / properties / uuid / description

Previous value: -"Share UUID (8-36 hex characters), usually discovered via search_by_ticker"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. Share id, usually discovered via search_by_ticker."

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "admission_date": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "created_at": {
+      "type": "string"
+    },
+    "currency": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "is_active": {
+      "type": "boolean"
+    },
+    "is_trading": {
+      "anyOf": [
+        {
+          "type": "boolean"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "issuer_name": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "issuer_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"
+        }
+      ]
+    },
+    "lot_size": {
+      "anyOf": [
+        {
+          "type": "number"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "name": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "nominal_value": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "security_kind": {
+      "const": "share",
+      "type": "string"
+    },
+    "share_kind": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "ticker": {
+      "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",
+    "ticker",
+    "name",
+    "issuer_uuid",
+    "issuer_name",
+    "security_kind",
+    "share_kind",
+    "nominal_value",
+    "currency",
+    "is_trading",
+    "is_active",
+    "admission_date",
+    "lot_size",
+    "created_at",
+    "updated_at"
+  ],
+  "type": "object"
+}

Changed1 schema field changedJun 25, 2026

changedInput schema / properties / uuid / description

Previous value: -"Share UUID (8-36 hex characters)"New value: +"Share UUID (8-36 hex characters), usually discovered via search_by_ticker"

First observedJun 9, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already cover safety (readOnlyHint, idempotentHint), so the bar is lower, and the description still adds real value by glossing is_trading as 'traded today, not historical liquidity' and warning that the uuid is not an RFC UUID. It stops short of noting rate limits or error behavior, but the semantics disclosed are non-obvious and useful.

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, front-loaded with the lookup key, then the payload fields, then the prerequisite. No filler, and the parenthetical clarifications are terse and load-bearing.

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?

A single-parameter read with an output schema present, so return values need no further explanation; the description nonetheless names the key fields, covering the agent's selection needs. Minor gap: no mention of what happens when the uuid is unknown or from another entity type.

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 coverage is 100% and the schema description already details the opaque hex format and points to search_by_ticker, so the description's '(field name: uuid)' is largely restating structured data. Baseline 3 applies when the schema carries the parameter burden.

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 ('Get a single BCSE exchange-listed share'), names the exact key field (uuid), and enumerates the returned attributes, so the agent knows precisely what entity class this covers. The entity type (share vs bond vs company vs token) is unambiguous against the sibling list.

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?

Explicitly routes the agent: 'Use search_by_ticker first when starting from a ticker,' which is the realistic entry path for this tool. No exclusion statement is given for the other *_get_by_uuid siblings, though the entity-type name makes the boundary reasonably clear.

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?