Skip to main content
Glama

neet_report

Read-onlyIdempotent

Full one-call report on NEET (Solana, canonical mint Ce2gx9KGXJ6C9Mp5b5x1sn9Mg87JwEbrQby4Zqo3pump) for agents acting for NEET holders. Sections, each with its source named: canonical identity verification (registry), market block (price, 24h change, market cap, liquidity, volume — DexScreener), safety summary (RugCheck score, flagged risks, LP lock), cluster and consensus state (are tracked smart-money wallets converging on NEET in the last 24h: consensus score, STRONG / FORMING / QUIET / EXITING signal, tracked buyer and seller counts, net flow, coverage), buying-pressure headline (net inflow needed for 2x / 5x / 10x from live pool reserves, constant-product math), holder-health headline (percent of sampled wallets in profit, total unrealized PnL, weighted average cost, MVRV, sample coverage), and recent CLONE sightings: other Solana mints trading on the NEET name, each marked CLONE with the canonical contract named. Sections degrade independently and honestly: a failed source is named in data_gaps and never blocks the rest. Independent tooling, not affiliated with the NEET token or its team; data only, no predictions or recommendations. Cost: $0.02 USDC per call via x402 (Base settlement; Solana settlement when configured) — no API key needed.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "neet_report"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Beyond the annotations (readOnly, idempotent, openWorld, non-destructive), the description discloses pricing and payment mechanics ($0.02 USDC per call via x402, Base settlement, no API key), partial-failure semantics (a failed source is named in data_gaps and never blocks the rest), and an independence disclaimer with no predictions. That is a rich, non-obvious behavioral picture an agent needs before spending money on a call.

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?

It is front-loaded with purpose and then systematically walks the returned sections, with each section annotated by its data source. It is dense and long, and the cost/payment detail sits at the very end where it would be better near the top, but almost every clause carries information.

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 parameters and no output schema, the description bears the full burden of describing return content, and it does so section by section with sources and stated degradation behavior. An agent can predict what it will receive and how gaps are reported without a schema.

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?

There are zero input parameters, so the baseline is 4 — nothing needs explaining. The description usefully pins the fixed subject (the canonical mint address) so the agent knows the call takes no arguments and is NEET-specific.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a concrete verb and resource — a full one-call report on NEET, naming the canonical Solana mint — and enumerates every section it returns (identity, market, safety, cluster consensus, buying pressure, holder health, clone sightings). The word 'Full' implicitly separates it from the 'lite' sibling, but no sibling is named explicitly, so differentiation is inferred rather than stated.

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

Usage Guidelines3/5

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

It states the audience ('agents acting for NEET holders') and the value proposition of a single consolidated call, which implies when to prefer it over piecemeal lookups. However, it never names neet_report_lite or neet_verify, nor says when a narrower or cheaper call is the better choice, so the routing decision is left to inference.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.