Skip to main content
Glama

SouthPow crypto & market data

buy_insider_GABC

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

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

Input Schema

NameRequiredDescriptionDefault
limitNoRows, 1-100 (default 20)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations at all, the description still carries the important behavioral facts: the tool is paid, the exact price and payment rail, that no auth or API key is required, and the underlying data provenance and filter ('open-market purchases... as filed'). It omits rate limits, pagination behavior, and what the paid response contains, which keeps it short of a 5.

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-loaded and dense: the paid status leads, then the dataset and filters, then price, access requirements, and endpoint. Every clause carries information, though the one-word 'Paid.' fragment and the bare URL at the end read as terse shorthand rather than polished prose.

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 zero-annotation, single-optional-param tool with no output schema, the description supplies the things an agent most needs: what data, from which filing type, at what cost, and with what access requirements. It does not describe the response fields or pagination, which is the main remaining gap given there is no output schema to fall back on.

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?

There is only one parameter and its schema description already covers it fully ('Rows, 1-100 (default 20)'). The description adds no meaning about how limit interacts with the paid call or result ordering, so the baseline of 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?

The description names a specific verb and resource ('insider BUYS from SEC Form 4') and constrains it precisely to open-market purchases by officers, directors, and 10% owners, plus the GABC ticker in the name. That distinguishes it from the generic buy_insider and from the many other buy_insider_<TICKER> siblings without needing to open 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?

Payment terms ('$0.25 USDC on Base, no account, no API key') give useful context for deciding whether to call it, but there is no explicit when-to-use or when-not guidance relative to buy_insider or the sibling ticker variants. The intended use (fetch GABC insider buys) is implied only by the name and entity description.

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