Skip to main content
Glama

Scam check

scam_check
Read-onlyIdempotent

Check a Base token (0x address) or URL for scam and rug risk before buying, or a wallet against the sanctions, USDC-blacklist and known-scam-deployer lists. Returns action OK | CAUTION | AVOID | VERIFY_MORE with the facts behind it and a ready-to-show summary. null means unknown, never safe. Free: 3 a day per IP (counted across the HTTP routes and MCP), then $0.008 per call via x402.

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": {
      "target": "<target>"
    },
    "name": "scam_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
quickNoFaster check (about 5 s) with fewer facts; skipped facts are null
targetYesBase 0x token address, wallet address or URL
compactNoNo summary text, no disclaimer, no null fields
amount_usdNoYour trade size in USD: adds a sell quote at that size (fields.sell_at_size) and the price impact

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / amount_usd / description
      Previous value: -"Your trade size in USD, for the price impact at that size"New value: +"Your trade size in USD: adds a sell quote at that size (fields.sell_at_size) and the price impact"
  2. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Goes well beyond the readOnly/idempotent annotations by disclosing the exact return vocabulary (OK | CAUTION | AVOID | VERIFY_MORE), the critical interpretation rule that null means unknown and never safe, and the full cost model: 3 free calls/day per IP shared across HTTP and MCP, then $0.008 via x402. Rate limits and payment/auth requirements are precisely the context annotations cannot carry.

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?

Three sentences, front-loaded with what is checked, then what is returned, then cost. Dense but every clause carries information; the only mild cramming is packing verdict semantics and null-handling into one sentence.

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 takes on the burden of explaining returns and does so: verdict enum, accompanying facts, ready-to-show summary, and null semantics. Combined with the cost/rate-limit disclosure, an agent has everything needed to call and interpret this tool.

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%, so quick, compact, amount_usd, and target are already fully documented in the schema. The description's 'null means unknown, never safe' rule adds interpretive value that connects to quick/compact, but it does not explain parameter tradeoffs beyond the schema, so the baseline 3 applies.

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

Purpose5/5

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

States a specific verb (check) and enumerates the exact resources it handles: Base 0x token address, URL, or wallet, plus which lists wallets are screened against (sanctions, USDC-blacklist, known-scam-deployers). It also names the output verdict taxonomy, so an agent can tell this apart from endpoint_check and verify_payment without opening a schema.

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?

'before buying' gives a clear usage context, and the two target modes (token/URL risk vs. wallet list screening) implicitly define when each applies. It does not explicitly say when to prefer endpoint_check or verify_payment instead, so it stops short of full alternative routing.

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