TokenBel Financial Data

token_get_by_uuid

Read-onlyIdempotent

Get a token's platform, sale status, price, rate and issuer. Tokens have no tickers; find the id with token_list. Example: {"uuid":"78c7e502"}.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`uuid`	Yes	TokenBel id (usually 8 hex chars, no hyphens; not an RFC UUID). Token id from token_list.

Output Schema

TableJSON Schema

Name	Required	Description
`name`	Yes
`sold`	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.
`status`	Yes
`currency`	Yes
`platform`	Yes
`is_active`	Yes
`created_at`	Yes
`updated_at`	Yes
`token_price`	Yes
`company_name`	Yes
`company_uuid`	Yes
`percent_rate`	Yes
`total_tokens`	Yes
`emission_stop`	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. Token id, usually discovered via token_list."New value: +"TokenBel id (usually 8 hex chars, no hyphens; not an RFC UUID). Token id from token_list."

Changed12 schema fields changedSep 11, 2026

removedOutput schema / properties / company_name / anyOf

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

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

removedOutput schema / properties / emission_stop / anyOf

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

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

removedOutput schema / properties / percent_rate / anyOf

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

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

removedOutput schema / properties / sold / anyOf

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

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

removedOutput schema / properties / token_price / anyOf

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

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

removedOutput schema / properties / total_tokens / anyOf

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

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

Changed2 schema fields changedJul 3, 2026

changedOutput schema / properties / sold / anyOf

Previous value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "type": "number"
+  },
+  {
+    "type": "null"
+  }
+]

changedOutput schema / properties / total_tokens / anyOf

Previous value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "type": "number"
+  },
+  {
+    "type": "null"
+  }
+]

Changed4 schema fields changedJul 2, 2026

changedOutput schema / properties / percent_rate / anyOf

Previous value: -[
-  {
-    "type": "number"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

changedOutput schema / properties / sold / anyOf

Previous value: -[
-  {
-    "type": "number"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

changedOutput schema / properties / token_price / anyOf

Previous value: -[
-  {
-    "type": "number"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

changedOutput schema / properties / total_tokens / anyOf

Previous value: -[
-  {
-    "type": "number"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

Changed2 schema fields changedJun 26, 2026

changedInput schema / properties / uuid / description

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

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "company_name": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "company_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"
+        }
+      ]
+    },
+    "created_at": {
+      "type": "string"
+    },
+    "currency": {
+      "type": "string"
+    },
+    "emission_stop": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "is_active": {
+      "type": "boolean"
+    },
+    "name": {
+      "type": "string"
+    },
+    "percent_rate": {
+      "anyOf": [
+        {
+          "type": "number"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "platform": {
+      "type": "string"
+    },
+    "sold": {
+      "anyOf": [
+        {
+          "type": "number"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "status": {
+      "type": "string"
+    },
+    "token_price": {
+      "anyOf": [
+        {
+          "type": "number"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "total_tokens": {
+      "anyOf": [
+        {
+          "type": "number"
+        },
+        {
+          "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",
+    "platform",
+    "status",
+    "percent_rate",
+    "token_price",
+    "currency",
+    "total_tokens",
+    "sold",
+    "emission_stop",
+    "company_uuid",
+    "company_name",
+    "is_active",
+    "created_at",
+    "updated_at"
+  ],
+  "type": "object"
+}

First observedJun 9, 2026

TDQS

A3.9/5.0

Behavior3/5

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

Annotations already declare readOnlyHint and idempotentHint, and the description's 'Get' wording is consistent with those. The description adds a small scoping note about token ids and tickers, but no additional behavioral details such as return format or side effects. With annotations covering safety, this is adequate.

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 three short, purposeful sentences: the first front-loads the operation, the second explains the prerequisite, and the third gives a concrete example. There is no filler or redundant restatement.

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?

For a one-parameter read-only getter with an output schema, the description is complete enough: it lists the returned fields, explains how to obtain the necessary uuid, and gives an example. The output schema covers return details, and annotations cover the safety profile.

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 schema already explains that uuid is a TokenBel id, usually 8 hex chars, not an RFC UUID, and sourced from token_list. The description's example reinforces this but adds little beyond the schema, so the baseline of 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?

The description states a specific verb and resource: 'Get a token's platform, sale status, price, rate and issuer.' It also clarifies that tokens have no tickers and that the id comes from token_list, which helps distinguish this tool from ticker-based search siblings.

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 provides implied workflow guidance: tokens have no tickers, so the agent should find the id with token_list before calling this tool. However, it does not explicitly state when to prefer this over token_trading_stats_get or other sibling getters.

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?