Agent Data API

Token safety and due diligence (EVM and Solana)

token_check

Read-onlyIdempotent

Check a token before trading. level=quick: one-line pre-trade verdict for up to 10 tokens ($0.02). level=safety (default): contract / mint safety: honeypot simulation, buy/sell tax, mint and freeze authority, Token-2022 traps, holders, liquidity ($0.015). level=max: safety plus the pre-trade verdict, one verdict and every red flag ($0.10). For wallets use address_check. Live data (chain, RugCheck, DexScreener); 1-30 s. Signals, not advice. Paid with x402 (USDC on Base, Polygon or Solana) per call; failed or empty calls are never charged.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "address": "<address>"
    },
    "name": "token_check"
  }
}

Input Schema

Name	Required	Description
`chain`	No	Chain of a 0x token (Solana mints are detected). Default ethereum.
`level`	No	Depth and price (default safety).
`address`	Yes	Token contract (0x...) or Solana mint. level=quick accepts up to 10, comma separated.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 30, 2026

changedInput schema / properties / level / enum

Previous value: -[
-  "quick",
-  "safety",
-  "report",
-  "max"
-]New value: +[
+  "quick",
+  "safety",
+  "max"
+]

AddedOct 24, 2026

TDQS

A4.5/5.0

Behavior3/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, open-world). The description adds real value beyond them: live data sources (chain, RugCheck, DexScreener), latency of 1-30 s, x402/USDC payment on three chains, and the billing guarantee that failed or empty calls are never charged. It omits return-shape detail despite no output schema, so it is strong but not complete.

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?

Front-loads the core action, then the level table, then the sibling redirect, then operational facts. Every clause (pricing, latency, billing guarantee, 'signals, not advice') carries information an agent or its caller needs; nothing is decorative.

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 no output schema, the description still describes the payload of each level (honeypot simulation, taxes, mint/freeze authority, Token-2022 traps, holders, liquidity) and the cost/latency/payment model. Nothing needed to call this correctly or set expectations is missing.

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 earns a bump by explaining what each level value actually produces and costs, far beyond the schema's terse 'Depth and price'. The comma-separated up-to-10-address trick for level=quick is reinforced and shown in context.

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+resource ('check a token before trading') and then enumerates exactly what each of the three levels returns, so the agent can tell the levels apart without opening the schema. It also explicitly names the sibling it is not ('For wallets use address_check').

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

Usage Guidelines5/5

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

Gives an explicit routing rule to a named alternative ('For wallets use address_check') plus per-level usage guidance tied to cost and depth. The agent knows both when to call this and when to call something else.

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

All Agent Data API 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?