Skip to main content
Glama

neet_verify

Read-onlyIdempotent

Verify any Solana mint against the NEET narrative: returns CANONICAL (it is the real NEET, Ce2gx9KGXJ6C9Mp5b5x1sn9Mg87JwEbrQby4Zqo3pump), CLONE (it trades on the NEET name but is a different contract; the canonical contract is named in the verdict), or NOT_NEET. Registry-driven: registered clones resolve by address even when the token is dead and has no market data. This is the anti-scam check to run before buying, quoting, or routing to anything named NEET: ticker copies are industrial-scale on Solana and at least one aggregator has mislabelled a dead clone as the official contract. Independent tooling, not affiliated with the NEET token or its team. Cost: $0.005 USDC per call via x402 (Base settlement; Solana settlement when configured).

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": {
      "mint": "<mint>"
    },
    "name": "neet_verify"
  }
}

Input Schema

NameRequiredDescriptionDefault
mintYesAny Solana mint address (base58, 32-44 chars) to check against the NEET narrative, e.g. 9MaKE8AQW2HjsQjLYgvkXc8PEWTQ43t5qj9Gc9VEpump (a known clone) or the canonical Ce2gx9KGXJ6C9Mp5b5x1sn9Mg87JwEbrQby4Zqo3pump.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior5/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive, open-world), and the description adds substantial context on top: registry-driven resolution that works even for dead tokens with no market data, the canonical contract address, a cost of $0.005 USDC per call with x402/Base settlement, and an independence disclaimer. Pricing, payment mechanism, and data provenance are exactly the behavioral facts annotations cannot convey.

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?

The verdict taxonomy is front-loaded in the first sentence and the operational facts (cost, settlement, independence) follow in a logical order. The sentence about ticker copies being 'industrial-scale' and an aggregator mislabelling a clone is persuasive framing rather than operational detail, which is minor bloat.

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 no output schema, the description correctly carries the burden of explaining the return values and does so by naming all three verdicts and noting that the canonical contract appears in the CLONE verdict. Cost and settlement are also covered; only the concrete response field names are left implicit.

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% with a documented mint parameter and base58 format, so the baseline is 3. The description adds real meaning beyond the schema by explaining that registered clones resolve by address even when the token is dead and has no market data, which tells the agent that dead or unlisted mints are still valid inputs.

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 gives a specific verb and resource ('Verify any Solana mint against the NEET narrative') and enumerates the three possible verdicts (CANONICAL, CLONE, NOT_NEET), so the agent knows exactly what comes back. It does not differentiate itself from the sibling tools neet_report and neet_report_lite, which is the only thing keeping this from a 5.

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?

It states a concrete trigger condition: 'the anti-scam check to run before buying, quoting, or routing to anything named NEET', which tells the agent when to reach for it. It gives no explicit when-not condition and does not name an alternative for adjacent reporting needs, so it stops short of a 5.

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.