Base Intel MCP

Token Balance

token_balance

Read-onlyIdempotent

How much of an ERC-20 token a wallet holds on Base, returned both human-formatted (using the token's decimals) and raw. Pass the token contract address and the holder address, both 0x + 40 hex. Example: USDC 0x833589fcd6edb6e08f4c7c32d4f71b54bda02913.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`token`	Yes	ERC-20 contract address on Base: 0x followed by 40 hex characters.
`address`	Yes	Wallet address whose balance to read: 0x followed by 40 hex characters.

Output Schema

TableJSON Schema

Name	Required	Description
`token`	No
`holder`	No
`symbol`	No
`balance`	No
`network`	No
`decimals`	No
`provenance`	No	Where this answer came from. served_at is when Datakoot answered (UTC); upstream lists the official sources consulted. Datakoot may serve a briefly cached copy, so the source's own observation can be older than served_at.
`balance_raw`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 8, 2026

addedOutput schema / properties / provenance

Added value: +{
+  "description": "Where this answer came from. served_at is when Datakoot answered (UTC); upstream lists the official sources consulted. Datakoot may serve a briefly cached copy, so the source's own observation can be older than served_at.",
+  "properties": {
+    "may_be_cached": {
+      "type": "boolean"
+    },
+    "publisher": {
+      "type": "string"
+    },
+    "served_at": {
+      "format": "date-time",
+      "type": "string"
+    },
+    "upstream": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    }
+  },
+  "type": "object"
+}

Changed1 schema field changedOct 3, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "properties": {
+    "balance": {},
+    "balance_raw": {},
+    "decimals": {},
+    "holder": {},
+    "network": {},
+    "symbol": {},
+    "token": {}
+  },
+  "type": "object"
+}

First observedSep 6, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, openWorld), so the bar is lower. The description still adds real value beyond them: it discloses that the result comes back in two forms (decimals-adjusted and raw) and pins the chain to Base, plus the address literal format.

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?

Two sentences, front-loaded with the core capability and the output shape, followed by an actionable example. Slight redundancy: the '0x + 40 hex' constraint is repeated verbatim from the two schema parameter descriptions.

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 simple two-address read with an output schema, the description gives chain, address format, result formatting, and a valid example — enough to invoke correctly. Only minor gaps remain (e.g., behavior on a non-ERC-20 or wrong-chain address), which edge cases rarely determine selection.

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%, so both parameters are already fully documented in the schema; baseline is 3. The description restates the 0x + 40 hex format and adds a worked USDC example, which is marginally useful but largely duplicates the schema text.

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 concrete operation (read how much of a specific ERC-20 token a specific wallet holds) with an explicit scope (Base, fixed token+holder pair). This is intrinsically distinguishable from token_info (token metadata) and address_report (broader wallet view), so an agent can route correctly without opening a schema.

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

Usage Guidelines2/5

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

The description explains how to fill the parameters but never says when to choose this tool over address_report or token_info, nor when it is not appropriate. No preconditions, no exclusions, no named alternatives are given.

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

All Base Intel 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.