Aayat AI

Token report cached ($0.05)

token-report-cached

Read-only

Full token report, cached tier (answers up to 15 minutes old, half price): safety (honeypot, taxes, owner powers), holders (concentration, exchange/fund/locked share), liquidity (depth, locks, pools), price action, social/news buzz and smart-money signals (trade sizes, buy pressure, exchange and fund flows, whale transfers), with an overall rating and headline. Base, Solana, Ethereum, BNB, Arbitrum, Polygon, Optimism, Avalanche. Fresh data: /token/report. Price: $0.05 in USDC per call (x402 or prepaid credits). Paid only (not in the free trial). Try token-safety free first.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`chain`	No	Blockchain: base, solana, ethereum, bsc, arbitrum, polygon, optimism, avalanche.	base
`address`	Yes	Token contract address (0x...) or Solana mint address.

Output Schema

TableJSON Schema

Name	Required	Description
`buzz`	Yes	0-100 buzz score, website and socials, paid DexScreener promotion and boosts, Hacker News mentions in 30 days.
`name`	No
`tier`	Yes
`chain`	Yes
`market`	Yes
`safety`	Yes
`symbol`	No
`address`	Yes
`holders`	No	Holder count, top-1/top-10 concentration, sellable top-10, supply by kind (exchange, fund/market maker, pool, locked, contract, wallet), labelled top holders.
`sources`	No
`summary`	Yes	Overall rating (avoid, caution, ok, unknown), one-line headline, highlights and risks.
`liquidity`	Yes	Total USD, depth rating, locked %, liquidity/market cap, top pools.
`disclaimer`	No
`smartMoney`	Yes	Bias (bullish/bearish/neutral), signals, exchange, DEX and fund/market-maker flows, large transfers, top traders (when available).
`generatedAt`	No
`priceAction`	Yes	Price, % change 5m/1h/6h/24h, trend, volume and buys/sells per window, buy/sell ratio, volume/liquidity.

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedSep 28, 2026
- addedOutput schema / properties / safety / properties / checksNotRun
```
Added value: +{
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}
```
- addedOutput schema / properties / safety / properties / score / description
```
Added value: +"null when the contract scan or liquidity data was unavailable"
```
- changedOutput schema / properties / safety / properties / score / type
```
Previous value: -"integer"New value: +[
+  "integer",
+  "null"
+]
```
- addedOutput schema / properties / safety / properties / verdictReason
```
Added value: +{
+  "type": "string"
+}
```
First observedSep 28, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations cover read-only/open-world/non-idempotent, and the description adds material traits beyond them: results can be up to 15 minutes stale, the exact price ($0.05 USDC via x402 or prepaid credits), that it is paid-only and excluded from the free trial. Cost, caching freshness, and payment model are the key behavioral facts an agent needs here.

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?

Purpose and caching/price framing are front-loaded, then contents, chains, alternatives, and price. It is dense but nearly every clause carries information; the chain enumeration and some parenthetical detail are slightly redundant with the schema.

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?

For a paid, cached, multi-signal report tool the description covers coverage scope, freshness, cost, payment method, supported chains, and alternatives. An output schema exists, so return-value detail is not required, and nothing an agent needs to call it 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?

Schema description coverage is 100% and the enum is fully documented in the schema, so the baseline is 3. The description's chain list duplicates the enum and adds no format guidance beyond what the schema already provides for address/chain.

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 resource ('Full token report, cached tier') and enumerates exactly what it covers (safety, holders, liquidity, price action, social/news, smart-money signals). It explicitly differentiates itself from the fresh sibling ('Fresh data: /token/report') and from token-safety, so an agent can distinguish it without opening any schema.

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 explicit when-to-use ('answers up to 15 minutes old, half price'), names the fresh alternative, states paid-only/not-in-free-trial, and routes to a free starting point ('Try token-safety free first'). When/when-not/alternatives are all present.

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

All Aayat AI 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?