Base Intel MCP

Token Info

token_info

Read-onlyIdempotent

ERC-20 token metadata on Base, read on-chain: name, symbol, decimals, and total supply, plus whether the address really behaves like an ERC-20. Use it to verify a token contract before trusting or displaying it. Input: the token contract address (0x + 40 hex).

Input Schema

TableJSON Schema

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

Output Schema

TableJSON Schema

Name	Required	Description
`name`	No
`token`	No
`symbol`	No
`network`	No
`decimals`	No
`is_erc20`	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.
`total_supply`	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": {
+    "decimals": {},
+    "is_erc20": {},
+    "name": {},
+    "network": {},
+    "symbol": {},
+    "token": {},
+    "total_supply": {}
+  },
+  "type": "object"
+}

First observedSep 6, 2026

TDQS

A4.1/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 description only needs to add context. It does: it discloses that the read happens on-chain and that the result includes a behavioral ERC-20 conformance check, which is a real semantic beyond the annotations. It does not describe behavior on invalid/non-ERC-20 addresses, but the bar is lower given annotation coverage.

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?

Three tight sentences, front-loaded with what is returned before the usage note. The trailing 'Input: the token contract address (0x + 40 hex)' duplicates the schema's parameter description, which is the one mildly wasteful element, keeping it from a 5.

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?

An output schema exists, so return values need no explanation, and the description still signals the conformance-check output. Purpose, when-to-use, and input format are all covered; the only gap is explicit sibling routing (e.g. token_balance for amounts), which is minor for a one-parameter read tool.

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% with a single required parameter, so the schema already documents the address format. The description restates the same 0x + 40 hex format without adding syntax, network caveats, or validation detail beyond the schema. Baseline 3 is appropriate.

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 (read), resource (ERC-20 token metadata), chain (Base), and enumerates the exact fields returned (name, symbol, decimals, total supply) plus a contract-validity signal. This clearly separates it from siblings like token_balance (balance only) and address_report, so an agent can pick it without opening the schema.

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?

Explicitly says when to use it: 'verify a token contract before trusting or displaying it.' That is a clear trigger condition. It does not, however, name an alternative tool or state when-not to use it (e.g. vs. token_balance for holdings), so it stops short of full routing guidance.

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.