Skip to main content
Glama
Sign In

Scrapling x402 Data Store

by io.github.bnth09productions-maker
OverviewDiscussionsAdmin

Hyperliquid perp funding rates ($0.01)

perp_funding
Read-only

PAID $0.01 USDC. Live Hyperliquid funding (1h, 8h, APR), direction, premium, mark/oracle price, open interest and 24h volume. Optional coin filter and limit.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "perp_funding"
  }
}

Input Schema

NameRequiredDescriptionDefault
coinNo
limitNo
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

A3.7/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 the non-obvious behavioral fact that the call costs $0.01 USDC and returns live (not cached) data. It stops short of stating rate limits or what happens when payment is absent.

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?

Two short sentences with the price front-loaded and the returned field list packed efficiently. Nearly zero waste, though 'Optional coin filter and limit' is a fragment that could carry more information in the same space.

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 usefully enumerates the returned fields, and the schema handles the payment key. Remaining gaps are the coin symbol format and the limit's bounds/default — minor for a simple single-endpoint read 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 only 33%, so the description should carry more weight. It mentions the coin filter and limit but adds no semantics beyond the property names — no expected coin symbol format, no default or max for limit, no ordering behavior. Only api_key is properly documented, and that comes from the schema, not the description.

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 resource (Hyperliquid perp funding) and enumerates the exact data fields returned (1h/8h/APR, direction, premium, mark/oracle, OI, 24h volume), which is far more than a restatement of the name. It never names the obvious sibling free_funding, so the free-vs-paid distinction must be inferred from the 'PAID $0.01 USDC' prefix.

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 'PAID $0.01 USDC' opener implies this is the paid counterpart to free_funding, and the schema's api_key description explains the payment alternatives. But the description itself gives no explicit when-to-use/when-not guidance or pointer to the free tool.

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