Skip to main content
Glama
Sign In

Scrapling x402 Data Store

by io.github.bnth09productions-maker
OverviewDiscussionsAdmin

DeFi protocol TVL lookup ($0.001)

lookup_protocol
Read-only

PAID $0.001 USDC. DeFi protocol TVL in USD from our own on-chain reads, per-chain TVL, category and chains (1d/7d change once history builds). Examples: q=aave, q=uniswap. Refreshed about every 30 min.

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": {
      "q": "<q>"
    },
    "name": "lookup_protocol"
  }
}

Input Schema

NameRequiredDescriptionDefault
qYesProtocol slug or name, e.g. aave-v3
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. Changed1 schema field changed
    • changedInput schema / properties / q / description
      Previous value: -"DefiLlama slug or name, e.g. aave"New value: +"Protocol slug or name, e.g. aave-v3"
  3. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds genuinely useful non-schema traits: $0.001 USDC cost, x402/per-call payment, on-chain sourcing, ~30 min refresh, and the caveat that 1d/7d change only appears once history builds. Missing only multi-match/ambiguity behavior.

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?

Front-loaded with the paid cost and the core output description, with examples and refresh cadence trailing. Dense but every clause carries information; minor run-on phrasing around the history caveat.

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?

With no output schema, the description adequately enumerates return fields and notes the history limitation. It is nearly complete for a single-required-param read tool, lacking only what happens on multiple name matches or an unknown slug.

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% and the q parameter already says 'Protocol slug or name, e.g. aave-v3'. The description's q=aave/q=uniswap examples restate that without adding format rules or disambiguation guidance. Baseline 3 applies since the schema carries the semantics.

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+resource (DeFi protocol TVL lookup) and enumerates the returned fields: TVL in USD, per-chain TVL, category, chains, and 1d/7d change. That field list clearly separates it from siblings like lookup_pool, lookup_yields, and defi_intel.

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?

Concrete invocation examples (q=aave, q=uniswap) plus the payment context make it clear how and when to call it. It stops short of routing guidance such as when to prefer defi_intel or lookup_pool instead, and gives no exclusions.

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