Skip to main content
Glama
Sign In

Scrapling x402 Data Store

by io.github.bnth09productions-maker
OverviewDiscussionsAdmin

US stock fundamentals from SEC filings ($0.005)

stock_fundamentals
Read-only

PAID $0.005 USDC. Use when an agent asks for a US company's revenue, net income, EPS, margins, cash, debt or shares outstanding. Latest annual + quarter + balance sheet from SEC EDGAR XBRL, ~10,000 tickers.

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_fundamentals"
  }
}

Input Schema

NameRequiredDescriptionDefault
tickerYesTicker (AAPL, BRK-B) or SEC CIK
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.2/5.0
Behavior4/5

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

Adds real context beyond the annotations: a hard price ($0.005 USDC per call), the payment path, and the upstream source that determines data freshness and scope. Annotations already cover read-only safety, so the paid-call disclosure is the value-add here. No rate limits, latency, or failure behavior for non-US/delisted tickers.

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?

Three short sentences, each earning its place: cost gate first, then the use case, then the data provenance. The most decision-critical fact (that it is paid) is front-loaded before the invocation criteria.

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 correctly compensates by naming what comes back (metrics, annual/quarter/balance-sheet scope). The payment mechanics are fully covered. Minor gap: response shape/units and what happens for unsupported tickers or non-US CIKs.

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 description coverage is 100%, so both parameters are already documented at the schema level, including ticker/CIK formats and the api_key/x402 payment fallback. The description adds only the ~10,000 ticker coverage breadth, which is marginal. Baseline 3 applies.

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?

Names the specific resource (US company fundamentals) and enumerates the exact metrics returned: revenue, net income, EPS, margins, cash, debt, shares outstanding. The data source (SEC EDGAR XBRL, latest annual + quarter + balance sheet) and coverage (~10,000 tickers) make it unmistakable against siblings like stock_price, stock_filings and stock_insiders.

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?

Gives an explicit trigger condition — 'Use when an agent asks for...' — tied to the specific metric list, which is genuinely actionable. It lacks any when-not condition or named alternative (e.g. use stock_price for quotes, stock_filings for raw filings), so routing is inferred rather than stated.

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