Skip to main content
Glama

SouthPow crypto & market data

buy_insider

Paid. Latest US insider BUYS from SEC Form 4 filings (open-market purchases by CEOs, CFOs, directors, 10% owners), collected live as filed. Filter by ticker. $0.01 USDC on Base. No account, no API key. URL https://southpow.media/v1/insider-buys.

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

Input Schema

NameRequiredDescriptionDefault
limitNoRows, 1-100 (default 20)
tickerNoOptional US stock ticker, e.g. NVDA

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations provided, the description carries the burden and does well: it discloses that the tool is paid, the exact cost ($0.01 USDC on Base), that no account or API key is needed, and that data is collected live as filed. Gaps remain around rate limits, error behavior, and response shape, but cost and auth model are unusually well surfaced.

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?

Front-loads the key 'Paid.' signal, then source, filter, price, and access model in a tight sequence. The endpoint URL is arguably redundant with the tool name but plausibly functional; otherwise no wasted wording.

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 two-parameter, zero-required read tool with no output schema, the description covers source, freshness, cost, and auth adequately. It stops short of describing what a returned row contains or how pagination interacts with limit, which would help an agent plan calls.

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?

Both parameters are fully documented in the schema (100% coverage), so the baseline is 3. The description only restates 'filter by ticker' and adds nothing on limit behavior or ticker format beyond the schema example.

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 resource and verb: latest US insider BUYS from SEC Form 4 filings, with the filer categories (CEOs, CFOs, directors, 10% owners) and openness of purchases spelled out. The 'insider-buys' framing distinguishes it from siblings like buy_crypto_price or buy_polymarket, though it never explicitly contrasts itself with them.

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?

Provides context that it is a paid endpoint and that ticker filtering is optional, which implies when it is useful. However, it gives no explicit when-to-use/when-not guidance and doesn't route the agent to alternatives such as search_facts or buy_search.

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