Skip to main content
Glama

Scan a link for drainers

scan_link
Read-only

Scan a URL or pasted post text for wallet-drainer and phishing patterns (fake claim/airdrop pages, lookalike domains, wallet-connect bait). Free: 20/day per IP; Pro: unlimited.

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": {
      "text": "<text>"
    },
    "name": "scan_link"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYesA URL or pasted post text
api_keyNoRugRadar Pro API key (optional; alternatively send Authorization: Bearer <key>).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, openWorld, non-destructive), and the description adds genuinely new behavioral context: a per-IP free quota of 20/day, unlimited Pro, and the implied API-key upgrade path. It does not disclose latency or what a hit vs. miss looks like, keeping it below a 5.

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?

Two compact sentences: capability and threat examples front-loaded, quota/plan constraints second. No filler or restated title text.

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?

No output schema exists, yet the description does not describe the shape of the verdict (score, flagged patterns, safe/unsafe), which is a real gap for a scanning tool. Everything else an agent needs — input kind, detection focus, rate limits, auth path — is present.

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 description coverage is 100%, so both 'text' and 'api_key' are already documented in the schema, and the description adds no syntax, format, or length guidance beyond it. Baseline 3 is appropriate when the schema carries the parameter semantics.

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 specific verb and resource ('Scan a URL or pasted post text') and enumerates the threat classes it detects (fake claim/airdrop pages, lookalike domains, wallet-connect bait), so an agent knows exactly what goes in and what it looks for. It stops short of explicitly differentiating itself from siblings like scan_wallet or check_token, relying on the input type (URL/text vs wallet/token) to imply the boundary.

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

Usage Guidelines3/5

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

Usage is inferable from the input definition — this is the tool for a link or pasted post rather than a wallet or token — but the description never states when to choose it over those siblings or any preconditions. The quota sentence implies repeated/volume use but is not routing 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.