TokenBel Financial Data

share_get_by_uuid

Read-onlyIdempotent

Get a BCSE share's ticker, issuer, nominal value and trading-today flag. Resolve tickers with search_by_ticker first. Example: {"uuid":"a97f1fed"}.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`uuid`	Yes	TokenBel id (usually 8 hex chars, no hyphens; not an RFC UUID). Share id from 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.

Changed1 schema field changedSep 25, 2026

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. Share id, usually discovered via search_by_ticker."New value: +"TokenBel id (usually 8 hex chars, no hyphens; not an RFC UUID). Share id from search_by_ticker."

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.1/5.0

Behavior3/5

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

The annotations already declare readOnlyHint=true and idempotentHint=true, so the read-only behavior is covered. The description adds no additional behavioral traits such as missing-record handling or error cases, but with annotations carrying the safety profile, a middle score is appropriate.

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 two short sentences plus a compact JSON example flex. It is front-loaded with the core purpose and includes an example without any filler or redundant restatement of the tool name.

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?

With one required parameter, a fully described schema, a read-only/idempotent annotation profile, an output schema present, and an example, the agent has everything needed to select and invoke this tool correctly. No essential contextual information is missing.

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%: the uuid parameter is already described as a TokenBel id, its format, and its source ('Share id from search_by_ticker'). The description only adds an example value, which reinforces but does not meaningfully extend the schema's semantic guidance.

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 states a specific verb and resource: 'Get a BCSE share's ticker, issuer, nominal value and trading-today flag.' The 'BCSE share' scope clearly distinguishes it from sibling get-by-uuid tools for bonds, companies, and tokens, and the enumerated fields tell the agent exactly what to expect.

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?

It gives concrete upstream guidance: 'Resolve tickers with search_by_ticker first,' which tells the agent a prerequisite and names the related lookup tool. It does not explicitly state when not to use this tool versus share_list or other siblings, so exclusion guidance is incomplete.

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?