Skip to main content
Glama

SouthPow crypto & market data

buy_insider_BPRE

Paid. BPRE 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/BPRE.

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

Input Schema

NameRequiredDescriptionDefault
limitNoRows, 1-100 (default 20)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full burden, and it does disclose the two traits that most affect agent behavior: the price ($0.25 USDC on Base) and the absence of auth requirements (no account, no API key), plus a direct URL for the x402 payment flow. It stops short of saying what happens on payment failure, whether a zero-result response is still billed, or what shape the payload takes, which leaves real operational questions unanswered.

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?

Four short clauses plus the URL, with the most decision-critical fact ('Paid.') front-loaded in a single word. Nothing is padded, and the price, payment rail, auth profile, and access URL each earn their 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 paid, single-parameter tool with no output schema, the cost and access mechanics are covered, but the return contract is not: the description never says what fields a filing record contains or whether an empty result still charges $0.25. Since no output schema exists to fall back on, that omission is a genuine gap an agent would want filled before spending money.

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% for the single optional limit parameter ('Rows, 1-100 (default 20)'), so the schema already explains range and default. The description adds nothing about limit — no note on pagination cost implications (e.g. whether limit affects the fixed $0.25 charge) and no guidance on a sensible value for an agent. Baseline 3 applies when the schema does all the work.

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?

States a specific verb and resource: BPRE insider BUYS sourced from SEC Form 4, with the qualifying buy types spelled out (open-market purchases by officers, directors, 10% owners). The ticker is embedded in the tool name and repeated in the URL, so an agent can tell it apart from the generic buy_insider entry point and the other per-ticker siblings without opening the schema.

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?

It conveys the decisive selection context an agent needs — that this is a paid call and how much it costs — which implicitly frames when to call it (when paid, ticker-specific data is acceptable). But it never states when NOT to use it: no mention of the free generic buy_insider, the timestamped-or-not nature of 'as filed', or what to do if the ticker has no Form 4 activity. Usage is implied rather than prescribed.

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