Skip to main content
Glama

TokenBel Financial Data

by io.github.AndreiDrang
OverviewDiscussionsAdmin

token_trading_stats_get

Read-onlyIdempotent

Get a token's primary-market tokens-sold daily series, totals and snapshot; not secondary trading. No dates = last 30 days; either date bound is allowed. Find the id with token_list. Example: {"uuid":"78c7e502"}.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
uuidYesTokenBel id (usually 8 hex chars, no hyphens; not an RFC UUID). Token id from token_list.
date_toNoInclusive YYYY-MM-DD end (>= start); defaults to today.
date_fromNoInclusive YYYY-MM-DD start; defaults to 30 days before end.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
modeYes
uuidYesTokenBel 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.
dailyYes
periodYes
totalsYes
currencyYes
platformYes
snapshotYes
security_kindYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / date_from / description
      Previous value: -"Range start date YYYY-MM-DD (inclusive). Defaults to date_to minus 30 days when omitted."New value: +"Inclusive YYYY-MM-DD start; defaults to 30 days before end."
    • changedInput schema / properties / date_to / description
      Previous value: -"Range end date YYYY-MM-DD (inclusive, >= date_from). Defaults to today when omitted."New value: +"Inclusive YYYY-MM-DD end (>= start); defaults to today."
    • 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."
  2. Changed8 schema fields changed
    • 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"
+]
  3. Changed2 schema fields changed
    • 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"
+}
  4. Added

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 the safety profile is covered. The description adds meaningful behavioral context: the output is a daily series plus totals and snapshot, the scope is primary-market only, and date bounds are optional with specific defaults. This enriches the agent's understanding beyond the annotations.

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?

Three short sentences with no filler. The primary purpose and exclusion are front-loaded, followed by default behavior and prerequisite lookup. The one-line JSON example is compact and earns its place.

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, idempotent tool with an output schema, the description covers everything an agent needs to select and call it: scope, exclusions, defaults, id source, and example. No missing pieces that would cause incorrect invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3. The description adds value by clarifying that uuid comes from token_list, that no dates means the last 30 days, and that either date bound alone is acceptable. The example JSON reinforces parameter usage.

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 opens with a specific verb and resource: 'Get a token's primary-market tokens-sold daily series, totals and snapshot'. It immediately distinguishes itself from siblings by stating 'not secondary trading', which disambiguates it from trading_stats_get and related market tools. This is a clear, specific purpose statement.

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 explicitly tells the agent when not to use it ('not secondary trading') and how to find the required id ('Find the id with token_list'). It also explains default date behavior and that either date bound is allowed. It stops short of naming the alternative tool (e.g., trading_stats_get) outright, but the exclusion is clear enough.

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 toolsInspect
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