Aayat AI

Full token report ($0.10)

token-report

Read-only

Everything about a token in one answer: safety, who holds it, liquidity, price action, whales and smart money, and news buzz, with an overall rating. ★ One of our best tools. Full token report, live: 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, in one call. 8 chains incl. Base, Solana, Ethereum. Cheaper 15-min cache: /token/report/cached. AI verdict: /token/report/deep. Price: $0.10 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.2/5.0

Behavior4/5

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

Annotations already establish readOnlyHint=true and openWorldHint=true, so safety is covered; the description adds cost ($0.10 USDC via x402 or prepaid credits), payment gating, chain coverage, and a live-vs-cached freshness distinction that is consistent with idempotentHint=false. It stops short of stating rate limits or auth specifics, but the behavioral surface is well disclosed.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the core purpose and good routing links, but the content inventory is duplicated almost verbatim ('safety...holders...liquidity...price action...whales/smart money...news') plus marketing filler ('★ One of our best tools'). Roughly a third of the text is redundant and could be cut without losing information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With an output schema present, return values needn't be described, and annotations cover the safety profile. Coverage of price, payment path, chain support, freshness variants, and alternative tools makes it complete for an agent deciding whether and how to call it; only rate limits/auth specifics are absent.

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%, so the enum and address format are fully documented in the schema itself. The description repeats the chain list ('8 chains incl. Base, Solana, Ethereum') without adding format, default, or validation detail beyond it. Baseline 3 is appropriate when the schema carries the full parameter 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?

Names a specific resource (token) and enumerates exactly what the report contains: safety, holders, liquidity, price action, whales/smart money, news buzz, plus an overall rating. It also distinguishes itself from siblings by naming token-safety (free), token-report-cached, and token-report-deep. An agent can route correctly 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 and when-to-use-alternatives guidance: use /token/report/cached for the cheaper 15-min version, /token/report/deep for an AI verdict, and 'try token-safety free first.' It also states the key exclusion – paid only, not in the free trial – which is exactly the kind of precondition an agent needs.

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?