Crypto Bot Audit + Market Data (x402 paid)

Explorer token profile

market_scout_token_profile

Read-onlyIdempotent

The explorer's own record for one ERC-20/721 token: name, symbol, type, decimals, holder count, total supply, circulating market cap, 24h volume and the USD exchange rate it quotes. Costs $0.001 USDC per call. Byte-identical to GET /market/scout-token-profile?chain=base&address=0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`chain`	No	which Blockscout explorer to ask (default "base")
`address`	Yes	target address, 0x + 40 hex [required]

Output Schema

TableJSON Schema

Name	Required	Description	Default
`ts`	No
`name`	No
`note`	No
`type`	No
`chain`	No
`found`	No
`stale`	No
`caveat`	No
`reason`	No
`source`	No
`symbol`	No
`address`	No
`holders`	No
`iconUrl`	No
`decimals`	No
`volume24h`	No
`reputation`	No
`totalSupply`	No
`exchangeRateUsd`	No
`circulatingMarketCap`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 25, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "address": {
+      "type": "string"
+    },
+    "caveat": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "chain": {
+      "type": "string"
+    },
+    "circulatingMarketCap": {
+      "type": "number"
+    },
+    "decimals": {
+      "type": "integer"
+    },
+    "exchangeRateUsd": {
+      "type": "number"
+    },
+    "found": {
+      "type": "boolean"
+    },
+    "holders": {
+      "type": "integer"
+    },
+    "iconUrl": {
+      "type": "string"
+    },
+    "name": {
+      "type": "string"
+    },
+    "note": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "reason": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "reputation": {
+      "type": "string"
+    },
+    "source": {
+      "type": "string"
+    },
+    "stale": {
+      "type": [
+        "boolean",
+        "null"
+      ]
+    },
+    "symbol": {
+      "type": "string"
+    },
+    "totalSupply": {
+      "type": "string"
+    },
+    "ts": {
+      "type": "string"
+    },
+    "type": {
+      "type": "string"
+    },
+    "volume24h": {
+      "type": "number"
+    }
+  },
+  "type": "object"
+}

AddedSep 24, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and idempotentHint=true, so the description does not need to repeat safety semantics. It adds value by disclosing the $0.001 USDC charge per call and stating that the response is byte-identical to a specific GET endpoint, which is useful behavioral context.

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 dense sentences with no filler. The purpose is front-loaded, followed by cost and endpoint identity. Every sentence 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?

With a full output schema, complete parameter documentation, and rich annotations, the description only needed to add cost and endpoint semantics, which it does. Nothing essential for calling this tool correctly is missing.

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?

The input schema already provides 100% parameter coverage, including the default chain and required address format. The description's endpoint example illustrates both parameters in context, but it does not add substantial semantic meaning beyond the schema.

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 states a specific resource ('the explorer's own record for one ERC-20/721 token') and enumerates exactly what fields are returned. It clearly distinguishes itself from sibling tools like market_scout_address_profile or chain_token_meta by focusing on a token profile with market metrics and an exchange rate.

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: it is for a single ERC-20/721 token profile and includes cost and an exact endpoint equivalence. It does not explicitly name alternatives or exclusion conditions, but the use case is unambiguous enough for an agent to select it appropriately.

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

All Crypto Bot Audit + Market Data (x402 paid) 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?