TokenBel Financial Data

token_trading_stats_get

Read-onlyIdempotent

Get primary-market sales statistics for a token by its TokenBel internal identifier (field name: uuid). Returns a per-day series of tokens sold (derived from the cumulative instrument_log.sold counter), range totals, and a token snapshot (status, token_price, percent_rate, sold_total, total_tokens, sold_pct). Find the id via token_list first. Always a date range: omit both dates for the last 30 days, or provide date_from and/or date_to. Secondary-market data is not included.

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. Token id, usually discovered via token_list.
`date_to`	No	Range end date YYYY-MM-DD (inclusive, >= date_from). Defaults to today when omitted.
`date_from`	No	Range start date YYYY-MM-DD (inclusive). Defaults to date_to minus 30 days when omitted.

Output Schema

TableJSON Schema

Name	Required	Description
`mode`	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.
`daily`	Yes
`period`	Yes
`totals`	Yes
`currency`	Yes
`platform`	Yes
`snapshot`	Yes
`security_kind`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed8 schema fields changedSep 11, 2026
- removedOutput schema / properties / snapshot / properties / percent_rate / anyOf
```
Removed value: -[
-  {
-    "type": "number"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / snapshot / properties / percent_rate / type
```
Added value: +[
+  "number",
+  "null"
+]
```
- removedOutput schema / properties / snapshot / properties / sold_pct / anyOf
```
Removed value: -[
-  {
-    "type": "number"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / snapshot / properties / sold_pct / type
```
Added value: +[
+  "number",
+  "null"
+]
```
- removedOutput schema / properties / snapshot / properties / token_price / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / snapshot / properties / token_price / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / totals / properties / avg_tokens_per_active_day / anyOf
```
Removed value: -[
-  {
-    "type": "number"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / totals / properties / avg_tokens_per_active_day / type
```
Added value: +[
+  "number",
+  "null"
+]
```

Changed2 schema fields changedJun 26, 2026

changedInput schema / properties / uuid / description

Previous value: -"Token UUID (8-36 hex characters), usually discovered via token_list"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": {
+    "currency": {
+      "type": "string"
+    },
+    "daily": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "date": {
+            "type": "string"
+          },
+          "tokens_sold": {
+            "type": "number"
+          }
+        },
+        "required": [
+          "date",
+          "tokens_sold"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "mode": {
+      "const": "range",
+      "type": "string"
+    },
+    "period": {
+      "additionalProperties": false,
+      "properties": {
+        "date_from": {
+          "type": "string"
+        },
+        "date_to": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "date_from",
+        "date_to"
+      ],
+      "type": "object"
+    },
+    "platform": {
+      "type": "string"
+    },
+    "security_kind": {
+      "const": "token",
+      "type": "string"
+    },
+    "snapshot": {
+      "additionalProperties": false,
+      "properties": {
+        "percent_rate": {
+          "anyOf": [
+            {
+              "type": "number"
+            },
+            {
+              "type": "null"
+            }
+          ]
+        },
+        "sold_pct": {
+          "anyOf": [
+            {
+              "type": "number"
+            },
+            {
+              "type": "null"
+            }
+          ]
+        },
+        "sold_total": {
+          "type": "number"
+        },
+        "status": {
+          "type": "string"
+        },
+        "token_price": {
+          "anyOf": [
+            {
+              "type": "string"
+            },
+            {
+              "type": "null"
+            }
+          ]
+        },
+        "total_tokens": {
+          "type": "number"
+        }
+      },
+      "required": [
+        "status",
+        "token_price",
+        "percent_rate",
+        "sold_total",
+        "total_tokens",
+        "sold_pct"
+      ],
+      "type": "object"
+    },
+    "totals": {
+      "additionalProperties": false,
+      "properties": {
+        "active_days": {
+          "type": "number"
+        },
+        "avg_tokens_per_active_day": {
+          "anyOf": [
+            {
+              "type": "number"
+            },
+            {
+              "type": "null"
+            }
+          ]
+        },
+        "tokens_sold": {
+          "type": "number"
+        }
+      },
+      "required": [
+        "tokens_sold",
+        "active_days",
+        "avg_tokens_per_active_day"
+      ],
+      "type": "object"
+    },
+    "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",
+    "security_kind",
+    "platform",
+    "currency",
+    "mode",
+    "period",
+    "snapshot",
+    "daily",
+    "totals"
+  ],
+  "type": "object"
+}

AddedJun 25, 2026

TDQS

A4.5/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 beyond that: the per-day series is derived from the cumulative instrument_log.sold counter, the date defaults, and the explicit exclusion of secondary-market data.

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?

Front-loaded with the core action, then ordered by identifier discovery, date-range rules, and scope exclusion. Dense but every sentence carries information; no filler.

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 read-only stats tool with a full schema and an output schema, nothing an agent needs to call it correctly is missing: the id source, date semantics, and scope boundary are all present. Return-value detail is a bonus rather than a requirement given the output schema.

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 three parameters are already documented in the schema, making 3 the baseline. The description mostly restates the date-range defaults already present in the schema, adding only the 'field name: uuid' hint.

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 primary-market sales statistics for a token) plus the identifier it keys on. It explicitly carves out scope by saying secondary-market data is not included, which cleanly separates it from the sibling trading_stats_get.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives the prerequisite ('Find the id via token_list first'), the default behavior ('omit both dates for the last 30 days'), and the alternative usage ('provide date_from and/or date_to'). It also names the exclusion condition (secondary-market data) that routes the agent elsewhere.

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?