Skip to main content
Glama

SouthPow crypto & market data

buy_insider_BOLD

Paid. BOLD insider BUYS from SEC Form 4 (open-market purchases by officers, directors, 10% owners), as filed. $0.25 USDC on Base. No account, no API key. URL https://southpow.media/v1/insider-buys/BOLD.

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": "buy_insider_BOLD"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoRows, 1-100 (default 20)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior3/5

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

No annotations are provided, so the description must carry the load; it does disclose the price, payment rail, and that no auth is required, plus the data source and that only buys (not sales) are returned. It omits payment flow mechanics (whether a 402 challenge must be handled, whether repeat calls recharge), rate limits, and freshness/latency of the filings.

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?

Three short sentences with the payment constraint front-loaded, which is the highest-value fact. The endpoint URL is arguably redundant given the tool name but is plausibly needed for the x402 payment flow, so it earns its place.

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?

For a single-parameter paid data tool with no output schema, the description covers cost and source but not the shape of the returned rows (filer, transaction date, shares, price), which an agent needs to decide whether this answers the user's question.

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 100% and the single 'limit' parameter is fully documented in the schema, so baseline is 3. The description adds nothing about paging, default ordering, or what the limit counts against.

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 and resource: insider BUYS from SEC Form 4, scoped to open-market purchases by officers, directors, and 10% owners, for the BOLD ticker. That distinguishes it from the generic buy_insider and from the many other ticker-specific siblings, though the description never explicitly names the pattern 'one tool per ticker'.

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?

Gives access context ('Paid', '$0.25 USDC on Base', 'No account, no API key') but no when-to-use guidance: it never says to prefer this over buy_insider for the same ticker, nor what to do when the ticker has no Form 4 buys.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources