Crypto Bot Audit + Market Data (x402 paid)

Does this token support gasless permit()

chain_permit_ready

Read-onlyIdempotent

DOMAIN_SEPARATOR() plus the owner's current nonce and whether permit() is in the code — the three inputs a signed-approval relayer needs before it can move funds without the holder paying gas. Costs $0.001 USDC per call. Chains: base, ethereum, arbitrum, bsc, polygon, optimism, avalanche. Byte-identical to GET /chain/permit-ready?chain=base&token=0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913&owner=0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913.

Input Schema

TableJSON Schema

Name	Required	Description
`chain`	Yes	chain key: base, ethereum, arbitrum, bsc, polygon, optimism, avalanche [required]
`owner`	Yes	address whose permit nonce to read [required]
`token`	Yes	token / NFT contract address [required]

Output Schema

TableJSON Schema

Name	Required	Description	Default
`ts`	No
`note`	No
`chain`	No
`nonce`	No
`owner`	No
`stale`	No
`token`	No
`caveat`	No
`reason`	No
`source`	No
`chainId`	No
`chainLabel`	No
`permitReady`	No
`implementation`	No
`domainSeparator`	No
`permitSelectorIn`	No
`hasPermitSelector`	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"
+      ]
+    },
+    "domainSeparator": {
+      "type": "string"
+    },
+    "hasPermitSelector": {
+      "type": "boolean"
+    },
+    "implementation": {
+      "type": "string"
+    },
+    "nonce": {
+      "type": "string"
+    },
+    "note": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "owner": {
+      "type": "string"
+    },
+    "permitReady": {
+      "type": "boolean"
+    },
+    "permitSelectorIn": {
+      "type": "string"
+    },
+    "reason": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "source": {
+      "type": "string"
+    },
+    "stale": {
+      "type": [
+        "boolean",
+        "null"
+      ]
+    },
+    "token": {
+      "type": "string"
+    },
+    "ts": {
+      "type": "string"
+    }
+  },
+  "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 establish read-only, idempotent, open-world, and non-destructive behavior. The description adds meaningful context beyond that: the $0.001 USDC cost, supported chains, and the byte-identical REST endpoint. This gives the agent practical operational knowledge not present in the 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?

Three dense sentences deliver the core output, use case, cost, chains, and an exact endpoint example. There is no filler or repetition of schema content. The most important information 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?

With an output schema present and annotations covering safety, the description provides everything else an agent needs: cost, supported chains, and a canonical example. No critical operational detail 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?

Schema coverage is 100% and each parameter has a clear description. The tool description adds a concrete example URL and chain list, but does not materially expand on the schema's parameter meanings. Baseline 3 is appropriate since the schema carries the parameter documentation burden.

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 identifies the tool's output: domain separator, owner nonce, and permit() code presence. It frames these as the three inputs a relayer needs, which distinguishes this tool from generic chain_nonce or chain_code tools. The title reinforces the specific gasless-permit question.

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 a clear use case: a signed-approval relayer checking whether it can move funds without the holder paying gas. It does not explicitly state when not to use this tool or name alternatives, but the context is specific 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?