Aayat AI

Token report deep ($0.25)

token-report-deep

Read-only

Deep token report: everything in /token/report (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)) plus top 25 labelled holders, more transfer history, top traders when available, and an AI analyst verdict (stance, summary, risks, positives, what to watch). Price: $0.25 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.
`analysis`	Yes	AI analyst verdict: stance, summary, key risks, positives, what to watch.
`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/5.0

Behavior4/5

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

Annotations cover the safety profile (readOnly, openWorld), and the description adds high-value context the annotations don't: cost ($0.25 USDC per call), payment mechanism (x402 or prepaid credits), and the fact it is excluded from the free trial. It doesn't address the idempotentHint=false nuance, but pricing/auth disclosure is substantial.

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-loads 'Deep token report' but then packs the content list into a deeply nested parenthetical and appends pricing and trial notes in the same breath. Every clause is informative, but the single run-on sentence is harder to scan than a structured list would be.

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?

An output schema exists, so return values needn't be explained, and the description still previews the AI verdict fields (stance, summary, risks, positives, what to watch). Pricing and alternative routing are covered; only the deep-vs-standard comparison is thin.

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% with only two parameters, so the schema fully documents chain and address. The description adds no syntax or format detail beyond it, making the baseline 3 appropriate.

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?

Specific verb+resource ('Deep token report') with an explicit enumeration of what it contains beyond the sibling token-report: top 25 labelled holders, more transfer history, top traders, and an AI analyst verdict. An agent can distinguish it from token-report and token-safety without opening schemas.

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?

Routes the agent to a free alternative ('Try token-safety free first') and clarifies paid-only status versus the free trial. It doesn't explicitly say when to prefer this over token-report or token-report-cached, so the deep-vs-standard choice is left partly to inference.

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?