Crypto Bot Audit + Market Data (x402 paid)

ERC-721 tokenURI for one id

chain_nft_token_uri

Read-onlyIdempotent

The metadata pointer a wallet will follow for a specific id, plus whether it is on-chain JSON or an off-host scheme. The string is returned as text — this endpoint never resolves it. Costs $0.001 USDC per call. Chains: base, ethereum, arbitrum, bsc, polygon, optimism, avalanche. Byte-identical to GET /chain/nft-token-uri?chain=base&token=0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913&tokenId=1.

Input Schema

TableJSON Schema

Name	Required	Description
`chain`	Yes	chain key: base, ethereum, arbitrum, bsc, polygon, optimism, avalanche [required]
`token`	Yes	NFT contract address [required]
`tokenId`	Yes	token id (decimal) [required]

Output Schema

TableJSON Schema

Name	Required	Description	Default
`ts`	No
`host`	No
`note`	No
`chain`	No
`found`	No
`stale`	No
`token`	No
`caveat`	No
`length`	No
`reason`	No
`scheme`	No
`source`	No
`chainId`	No
`tokenId`	No
`tokenUri`	No
`chainLabel`	No
`fetchedByUs`	No
`isOnChainJson`	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": {
+    "caveat": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "chain": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "chainId": {
+      "anyOf": [
+        {
+          "type": "integer"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "chainLabel": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "fetchedByUs": {
+      "type": "boolean"
+    },
+    "found": {
+      "type": "boolean"
+    },
+    "host": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "isOnChainJson": {
+      "type": "boolean"
+    },
+    "length": {
+      "type": "integer"
+    },
+    "note": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "reason": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "scheme": {
+      "type": "string"
+    },
+    "source": {
+      "type": "string"
+    },
+    "stale": {
+      "type": [
+        "boolean",
+        "null"
+      ]
+    },
+    "token": {
+      "type": "string"
+    },
+    "tokenId": {
+      "type": "string"
+    },
+    "tokenUri": {
+      "type": "string"
+    },
+    "ts": {
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

AddedSep 24, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Annotations already mark readOnlyHint, idempotentHint, and destructiveHint, but the description adds critical behavior: the endpoint never resolves the URI, returns the string as text, and costs $0.001 USDC per call. This goes well beyond the annotations and gives the agent essential operational knowledge.

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 tight and information-dense: each sentence delivers a distinct fact (return semantics, non-resolution, cost, chain support, endpoint equivalence). No fluff, and the key behavior is front-loaded.

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 schema coverage of 100%, an output schema is present, and annotations cover safety/idempotency, the description supplies all remaining essentials: exact output semantics, cost, supported chains, and a byte-identical reference call. An agent can invoke this correctly without further research.

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 providing a concrete example URL (chain=base&token=0x...&tokenId=1) that clarifies expected formats for all three parameters, and it enumerates valid chain keys in the description, reinforcing 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 clearly states the tool returns the metadata pointer (tokenURI) for a specific ERC-721 id and whether it is on-chain JSON or off-host. This distinguishes it from siblings like chain_1155_uri (ERC-1155) and chain_nft_meta by the explicit 'metadata pointer' scope and the title's ERC-721 designation.

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

Usage Guidelines3/5

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

The intended use is implied—'the metadata pointer a wallet will follow for a specific id'—and the cost and chain list add practical context. However, it does not explicitly differentiate from alternatives like chain_1155_uri or chain_nft_meta, nor state when not to use it. The 'Byte-identical' note compares to an HTTP endpoint, not a sibling tool.

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?