Hive Intelligence MCP

Get Token Price

get_token_price

Read-only

Current price for one token. Pass token as a CoinGecko id or symbol ("bitcoin", "BTC"), or pass chain + address for a specific contract. Returns price, market cap, and 24h change with provider provenance.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_token_price"
  }
}

Input Schema

Name	Required	Description
`chain`	No	Chain name for the contract-address variant, for example "eth", "base", "bsc", or "solana".
`token`	No	CoinGecko coin id or ticker symbol, for example "bitcoin" or "BTC". Omit when passing chain + address.
`address`	No	Token contract address; requires chain.
`vs_currency`	No	Quote currency. Default "usd".
`response_format`	No	concise (default) returns the trimmed essentials; detailed returns the full provider payload. json and markdown, the platform-wide values every other tool advertises, are accepted and treated as concise.

Output Schema

Name	Required	Description	Default
`price`	No
`token`	No
`market_cap`	No
`vs_currency`	No
`source_receipt`	Yes
`change_24h_percent`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedSep 15, 2026

changedInput schema / properties / response_format / description

Previous value: -"Output format: 'json' for structured data (default) or 'markdown' for human-readable text."New value: +"concise (default) returns the trimmed essentials; detailed returns the full provider payload. json and markdown, the platform-wide values every other tool advertises, are accepted and treated as concise."

changedInput schema / properties / response_format / enum

Previous value: -[
-  "json",
-  "markdown"
-]New value: +[
+  "concise",
+  "detailed",
+  "json",
+  "markdown"
+]

Changed1 schema field changedSep 14, 2026
- changedInput schema / additionalProperties
```
Previous value: -falseNew value: +true
```

Changed1 schema field changedAug 22, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "properties": {
+    "change_24h_percent": {
+      "type": "number"
+    },
+    "market_cap": {
+      "type": "number"
+    },
+    "price": {
+      "type": "number"
+    },
+    "source_receipt": {
+      "additionalProperties": true,
+      "properties": {
+        "fetched_at": {
+          "format": "date-time",
+          "type": "string"
+        },
+        "provider": {
+          "type": "string"
+        },
+        "runtime_status": {
+          "enum": [
+            "ok",
+            "invalid_input",
+            "missing_key",
+            "plan_required",
+            "rate_limited",
+            "degraded",
+            "failing"
+          ],
+          "type": "string"
+        }
+      },
+      "required": [
+        "provider",
+        "runtime_status",
+        "fetched_at"
+      ],
+      "type": "object"
+    },
+    "token": {
+      "type": "string"
+    },
+    "vs_currency": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "source_receipt"
+  ],
+  "type": "object"
+}

First observedAug 18, 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=true and destructiveHint=false, establishing this is a safe read operation. The description adds useful behavioral context by explaining the input variants and the return payload shape (price, market cap, 24h change, provider provenance). It does not hide mutation or side effects, and there is no contradiction with 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?

The description is three short sentences with no filler. It front-loads the core purpose, then immediately gives invocation guidance and return summary. Every sentence earns its place, and the structure makes it easy for an agent to parse quickly.

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?

Given the schema already covers all parameter details and an output schema exists, the description is complete enough for correct invocation. It covers both accepted input modes, the default quote currency context is in the schema, and the return fields are stated. The only implicit requirement—that either token or chain+address should be supplied—is conveyed clearly through 'Pass token... or pass chain + address...'.

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 schema already documents each parameter and defaults. The description adds important semantic meaning beyond the schema by explaining the relationship between token and chain+address: the caller can pass a CoinGecko id/symbol OR a chain/address pair, which is crucial for correct invocation. response_format is fully described in the schema, so no additional description is needed there.

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 action and resource: 'Current price for one token.' It clearly distinguishes this from sibling tools like check_token_safety and get_wallet_portfolio by stating what it returns (price, market cap, 24h change, provider provenance) and the two accepted input modes (CoinGecko id/symbol or chain+address).

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?

The description gives clear context for when to call this tool: whenever you need the current price of a single token. It does not explicitly name sibling alternatives or state when not to use it, but the 'for one token' scope and distinct return fields make the usage context clear enough without exclusions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Hive Intelligence MCP 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.