Skip to main content
Glama
Sign In

Scrapling x402 Data Store

by io.github.bnth09productions-maker
OverviewDiscussionsAdmin

Yield pool lookup ($0.001)

lookup_pool
Read-only

PAID $0.001 USDC. One on-chain DeFi lending pool (Aave v3/Compound v3/Moonwell/Morpho Blue) by pool id protocol:chain:token_address, e.g. aave-v3:base:0x833589fcd6edb6e08f4c7c32d4f71b54bda02913: supply/borrow APY, utilization, TVL, impermanent-loss risk and risk score. 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": {
      "pool_id": "<pool_id>"
    },
    "name": "lookup_pool"
  }
}

Input Schema

NameRequiredDescriptionDefault
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'].
pool_idYes

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/5.0
Behavior5/5

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

The description provides critical behavioral context beyond the hints, specifically the cost ('PAID $0.001 USDC') and the data freshness ('Refreshed about every 30 min'). This gives the agent vital information regarding execution cost and data latency.

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?

The definition is highly efficient. It front-loads the value proposition (cost), immediately defines the scope, provides a working example of the input format, and lists the key metrics returned, all in a concise flow.

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?

Even without an output schema, the description is exceptionally complete by listing all the returned metrics (APY, utilization, TVL, risk score). The required input format and the rate/cost constraints are all addressed.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Since schema coverage is only 50%, the description is crucial. It defines the complex `pool_id` format (protocol:chain:token_address) and clarifies the function of the optional `api_key` parameter (prepaid vs. pay-per-call).

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?

The description clearly identifies the resource (DeFi lending pool), the action (lookup), and the exact format of the required input ID using a complete example (aave-v3:base:0x...). This makes the tool highly specific and distinct.

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?

The description is clear on what the tool does, but it doesn't explicitly state when to use it versus a closely related sibling tool. It focuses on defining the scope rather than offering directional advice for usage choice.

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