Skip to main content
Glama

Clearsignal Labs Token Scam Screen

List tokens that pass the screen

list_passing_tokens
Read-onlyIdempotent

Solana tokens that currently pass the automated scam screen, best score first, with warnings. Passing lowers but does not remove rug risk. NFA/DYOR.

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

Input Schema

NameRequiredDescriptionDefault
limitNoHow many tokens to return (1-50)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive, closed-world behavior, yet the description adds real value beyond them: results are sorted best-score-first and each entry carries warnings. The caveat that a passing score only lowers rug risk is genuine behavioral context an agent would otherwise over-trust, though pagination/truncation behavior beyond the limit cap is unstated.

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?

Two short sentences, front-loaded with the resource and scope, with zero padding. The trailing "NFA/DYOR" acronym is a disclaimer rather than operational information and is the one piece that doesn't strictly earn its place for an agent reader.

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?

For a zero-required-param, read-only list tool with no output schema, the description covers what is returned, in what order, and with what caveats. It would be fully complete if it clarified whether the list is exhaustive or capped, but nothing required to call it correctly is missing.

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 the single limit parameter fully documented (1-50, default 10), so the schema carries the parameter burden. The description adds no additional meaning about limit, only the implicit fact that ordering is fixed rather than caller-controlled.

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?

Names a concrete resource (Solana tokens passing the automated scam screen) plus ordering ("best score first") and content ("with warnings"), so the agent knows exactly what comes back. It does not contrast itself with check_token or check_wallet, leaving sibling differentiation to the names alone.

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

Usage Guidelines2/5

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

There is no explicit when-to-use guidance: no statement that this is the discovery/listing entry point and check_token is the per-token deep dive. The only guidance-adjacent content is the risk caveat ("Passing lowers but does not remove rug risk. NFA/DYOR"), which informs interpretation but not tool selection.

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