Skip to main content
Glama
Sign In

Scrapling x402 Data Store

by io.github.bnth09productions-maker
OverviewDiscussionsAdmin

Insider buys/sells from SEC Form 4 ($0.005)

stock_insiders
Read-only

PAID $0.005 USDC. Use when an agent asks whether insiders are buying or selling a stock. Parsed Form 4: insider, role, code, shares, price, value, 10b5-1 flag, buy/sell totals.

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

Input Schema

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

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?

Beyond the readOnlyHint/openWorldHint annotations, the description discloses the cost ($0.005 USDC) up front and enumerates the returned fields including the 10b5-1 flag, which is genuinely useful payload context. It does not mention rate limits, pagination, or the free-sibling alternative, and payment mechanics are left to the schema.

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 compact clauses: price first, then the triggering question, then the payload contents. Zero filler and the cost — the most decision-critical fact — is front-loaded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the field enumeration usefully substitutes for a return spec, and the price disclosure matters for a paid tool. However, three of four parameters remain unexplained and there is no note on what happens for tickers with no Form 4 activity.

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

Parameters2/5

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

Schema coverage is only 25% — API-key auth is documented in the schema, but ticker, limit, and open_market have no descriptions anywhere. The description lists output fields rather than explaining parameters and never clarifies whether open_market filters to open-market purchases or whether limit caps rows.

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?

States a specific verb-scope ('insiders are buying or selling a stock') and the exact data source (parsed SEC Form 4), plus the concrete fields returned. Scope is clear enough to separate it from broad siblings like stock_filings, though no sibling is named explicitly.

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?

'Use when an agent asks whether insiders are buying or selling a stock' is an explicit, actionable trigger. No when-not conditions or named alternatives (e.g., stock_filings for non-Form-4 filings) are given, so it stops short of a 5.

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