TokenBel Financial Data

company_get_by_uuid

Read-onlyIdempotent

Get a single company catalogue row by its TokenBel internal identifier (field name: uuid). Returns name, full_name, UNP (Belarusian tax ID), industry, logo, and activity flag. Companies are not always the same row as securities issuers; use search_by_name to discover both companies and issuers.

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. Company id, usually from search_by_name entity_type="company".

Output Schema

TableJSON Schema

Name	Required	Description
`unp`	Yes
`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.
`address`	Yes
`industry`	Yes
`full_name`	Yes
`is_active`	Yes
`logo_path`	Yes
`created_at`	Yes
`updated_at`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed10 schema fields changedSep 11, 2026

removedOutput schema / properties / address / anyOf

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

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

removedOutput schema / properties / full_name / anyOf

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

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

removedOutput schema / properties / industry / anyOf

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

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

removedOutput schema / properties / logo_path / anyOf

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

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

removedOutput schema / properties / unp / anyOf

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

addedOutput schema / properties / unp / type

Added value: +[
+  "string",
+  "null"
+]

Changed2 schema fields changedJun 26, 2026

changedInput schema / properties / uuid / description

Previous value: -"Company UUID (8-36 hex characters), usually from search_by_name entity_type=\"company\""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. Company id, usually from search_by_name entity_type=\"company\"."

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "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"
+}

Changed1 schema field changedJun 25, 2026

changedInput schema / properties / uuid / description

Previous value: -"Company UUID (8-36 hex characters)"New value: +"Company UUID (8-36 hex characters), usually from search_by_name entity_type=\"company\""

First observedJun 9, 2026

TDQS

A4.1/5.0

Behavior4/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 real behavioral context: the exact set of returned fields and the semantic caveat that a company row is not necessarily the same entity as a securities issuer, which prevents an agent from conflating the two namespaces. It does not describe behavior when the id is absent (null vs error), leaving a minor gap.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three tight sentences, front-loaded with the verb and key field, then returns, then the disambiguation note. The returned-field enumeration is partly redundant given an output schema exists, which slightly dilutes it, but nothing is padding.

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 single-param read tool with an output schema and clear annotations, the description covers what it retrieves, how to obtain the id, and how it differs from issuer lookups. The only omission is explicit not-found/error behavior, which is minor and often unnecessary on a standard catalogue read.

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 uuid property description already explains that it is an opaque 8-char hex string, not an RFC UUID, and where it comes from. The description only restates the identifier and its source, adding no syntax or format detail beyond the schema, so the baseline 3 applies.

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 company catalogue row by its TokenBel internal identifier'), names the key field (uuid), and enumerates the returned attributes. The closing note that companies are not always the same row as securities issuers distinguishes it from share_get_by_uuid / bond_get_by_uuid.

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?

Tells the agent where the identifier comes from ('use search_by_name to discover both companies and issuers'), which is the key prerequisite for calling this tool. It does not explicitly contrast with company_list (browse all) or state the failure mode when the id is unknown, so it stops short of full when/when-not 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?