Skip to main content
Glama
Sign In

Scrapling x402 Data Store

by io.github.bnth09productions-maker
OverviewDiscussionsAdmin

Base token scam check ($0.005)

lookup_token_risk
Read-only

PAID $0.005 USDC. Base token scam check: verdict go / caution / avoid, honeypot / cannot-sell, mintable, buy/sell tax and a 0-100 risk score. No charge if the scan fails. Example: address=0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913. Cached scan, else live on-chain scan with swap simulation (about 3-8 s).

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

Input Schema

NameRequiredDescriptionDefault
addressYes0x... Base token contract
api_keyNoOptional prepaid key (sk_scrapling_...) or catalog pass token (sdp_..., from pass_day/pass_month). Otherwise pay per call with x402 via _meta['x402/payment'].

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / api_key / description
      Previous value: -"Optional prepaid key (sk_scrapling_...). Otherwise pay per call with x402 via _meta['x402/payment']."New value: +"Optional prepaid key (sk_scrapling_...) or catalog pass token (sdp_..., from pass_day/pass_month). Otherwise pay per call with x402 via _meta['x402/payment']."
  2. Added

TDQS

A4/5.0
Behavior5/5

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

Goes well beyond the readOnlyHint/openWorldHint annotations: it discloses the $0.005 USDC charge, the no-charge-on-failure policy, that results may come from a cache or a live on-chain swap simulation, and the 3-8 s latency. Those are exactly the operational facts an agent needs before deciding to pay for a call.

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?

The description is dense and front-loads the paid gate and purpose, then outputs, refund policy, example and latency. Every clause carries information, though the price appears both in the title and the first word of the description and the sentence reads as a compressed run-on.

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 steps in to enumerate the return payload (verdict tiers, honeypot/cannot-sell, mintable, buy/sell tax, risk score) and covers cost, caching, latency and failure handling. Nothing material is missing for a two-parameter paid lookup.

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 address and api_key (including the sk_/sdp_ prefixes and x402 payment path) are already documented in the schema. The description adds only a sample address value and reinforces that the target is a Base token contract, which is a marginal supplement rather than new 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?

The description names a specific resource and scope: a Base-chain token scam/risk check returning a verdict, honeypot flags, taxes and a 0-100 score. An agent can immediately tell this from siblings like whale_moves or address_poisoning. It does not, however, differentiate itself from the closely related token_verdict sibling, so it stops short of a 5.

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 implied by the stated outputs (pre-trade scam screening of a Base token) and the pricing/latency notes give practical context. There is no explicit when-to-use or when-not-to-use guidance, and no mention of when to prefer token_verdict or dd_quick instead, leaving the agent to infer.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Scrapling x402 Data Store toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources