Skip to main content
Glama

Clearsignal Labs Token Scam Screen

Check a wallet against the bad-wallet list

check_wallet
Read-onlyIdempotent

Is this Solana wallet (usually a token creator) on our heuristic bad-wallet list? Not being listed does NOT mean a wallet 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": {
      "address": "<address>"
    },
    "name": "check_wallet"
  }
}

Input Schema

NameRequiredDescriptionDefault
addressYesSolana wallet address (base58, 32-44 chars)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the description earns credit for the additional epistemic caveat: the list is heuristic and a negative result is not an endorsement. That is context an agent cannot get from the annotations and materially affects how the answer should be reported.

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 short sentences, front-loaded with the core question, followed by the two caveats that matter. Nothing is redundant with the title or annotations.

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?

The tool is simple (one required parameter, no output schema) and the description is sufficient to call it correctly. The only gap is not stating what the response looks like — a boolean flag versus a flagged-listing with details — which the absence of an output schema leaves to inference.

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?

With one parameter and 100% schema description coverage, the schema already documents the address format (base58, 32-44 chars). The description adds only the 'usually a token creator' framing and no syntax or format detail beyond the schema, so the baseline of 3 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?

The description poses a specific verb+resource question — whether a given Solana wallet appears on the heuristic bad-wallet list — and characterizes the typical subject ('usually a token creator'). The wallet-vs-token distinction separates it from check_token implicitly, but no sibling is named explicitly.

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?

'usually a token creator' gives the agent a concrete scenario for reaching for this tool, and the 'not being listed does NOT mean a wallet is safe' line guides interpretation of the result. There is no explicit when-not or pointer to an alternative tool, 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.

Resources