Skip to main content
Glama

Clearsignal Labs Token Scam Screen

Check a Solana token

check_token
Read-onlyIdempotent

Look up the latest scam-screen verdict (PASS/FAIL/SKIP), 0-100 score and reasons for a Solana token mint, from our own database. Read-only, no live lookups: a mint we have not screened recently returns found=false, which does NOT mean the token is safe. NFA/DYOR.

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": "check_token"
  }
}

Input Schema

NameRequiredDescriptionDefault
mintYesSolana token mint address (base58, 32-44 chars)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already disclose read-only, idempotent, non-open-world behavior, so the bar is lower. The description still adds substantial context beyond them: it defines the verdict enum and score range, explains the data source (own database, no live lookups), and explicitly warns that found=false is not a safety signal — a real behavioral trap an agent must know.

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

Conciseness5/5

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

Three tight sentences: what it returns first, then the data-source behavior and caveat, then the disclaimer. Every sentence carries information an agent needs, and nothing is wasted.

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 output schema, the description correctly takes on the job of explaining return values (verdict, score, reasons, found flag). For a one-parameter read-only tool, that makes it complete — an agent knows what it will get and how to interpret edge cases.

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%, so the schema already documents the mint address format. The description adds the domain framing ('Solana token mint') but no new syntax or constraints beyond what the schema provides. With a single fully documented parameter, the baseline of 3–4 applies.

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?

States a specific verb (look up) and resource (the scam-screen verdict for a Solana token mint) and specifies the return shape (PASS/FAIL/SKIP, 0-100 score, reasons) from 'our own database.' It does not explicitly name or differentiate against siblings like list_passing_tokens, so it falls short of the top bar.

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?

Gives a clear usage context: this is a cached-database lookup with no live checks, implying you should not use it when freshness matters. It also front-loads the important 'found=false does NOT mean safe' caveat. However, it never names an alternative tool to use instead, so it stops short of explicit when-to-use/when-not guidance.

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.

Resources