Skip to main content
Glama
Sign In

Scrapling x402 Data Store

by io.github.bnth09productions-maker
OverviewDiscussionsAdmin

On-chain stock/ETF price ($0.001)

stock_price
Read-only

PAID $0.001 USDC. Use when an agent needs a current price for a major US stock or ETF (TSLA, NVDA, SPY...) from Chainlink oracle feeds read on-chain.

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": {
      "ticker": "<ticker>"
    },
    "name": "stock_price"
  }
}

Input Schema

NameRequiredDescriptionDefault
tickerYes
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
Behavior4/5

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

Annotations already declare this is a read-only operation, so the description adds useful behavioral context beyond them: the call costs $0.001 USDC and reads Chainlink oracle feeds on-chain. It does not cover freshness, ticker coverage limits, or failure behavior, but the core payment and source traits are disclosed.

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 sentences with zero waste. The paid cost is front-loaded, followed immediately by the usage condition and data source, so the agent can decide quickly.

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?

For a simple two-parameter read-only price lookup, the description provides the essential context: cost, asset scope, examples, and on-chain oracle source. It is complete enough to invoke correctly, with only minor gaps around freshness and ticker format.

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 50%: api_key is well documented in the schema, while ticker has no schema description. The description partially compensates by giving ticker examples (TSLA, NVDA, SPY) and restricting the scope to major US stocks/ETFs, but it does not specify ticker formatting or mention api_key behavior.

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 states a specific verb and resource: fetching a current price for a major US stock or ETF, sourced from Chainlink oracle feeds read on-chain. It distinguishes itself from generic price tools by specifying on-chain oracle pricing and a paid cost, though it does not explicitly name the closest free sibling.

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?

It gives a clear usage condition: use when an agent needs a current price for a major US stock or ETF. It does not give explicit exclusions or name alternatives such as free_stocks, so the agent must infer that free alternatives exist rather than being routed to them.

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