Skip to main content
Glama

SouthPow crypto & market data

buy_insider_LEO

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

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

Input Schema

NameRequiredDescriptionDefault
limitNoRows, 1-100 (default 20)

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 behavioral burden and does well: it discloses cost ($0.05 USDC on Base), that no account or API key is required, the upstream source (SEC Form 4) and the exact URL endpoint. What it omits is what the response looks like and whether the paid call is idempotent or repeated calls charge again.

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?

Very compact and front-loaded: the paid flag, the dataset scope, the price, the auth requirement, and the endpoint each appear once with no filler. The fragmented style ('Paid.', 'No account, no API key.') is terse but readable and puts the most decision-relevant facts early.

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 single-parameter paid data endpoint, the description covers source, scope, cost, auth, and URL, which is most of what an agent needs to decide and pay. The remaining gap is return shape and freshness, which is a modest omission 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?

Schema description coverage is 100% and the single 'limit' parameter is already documented as 'Rows, 1-100 (default 20)'. The description adds no meaning about the limit or about ordering/pagination of rows, so the schema does all the work and baseline 3 applies.

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-like scope: 'LEO insider BUYS from SEC Form 4 (open-market purchases by officers, directors, 10% owners), as filed.' This tells an agent exactly what dataset is returned, and the 'open-market purchases' qualifier implicitly excludes sales/grants. It does not explicitly say how it relates to the base buy_insider tool or to sibling ticker variants, so differentiation is inferred from the name rather than stated.

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?

Usage is only implied: an agent infers it should call this when it wants Form 4 open-market insider purchases for LEO specifically. There is no explicit when-to-use guidance, no statement about the aggregate buy_insider alternative, and no note on freshness or whether the feed is historical or current. The payment and no-account notes are practical context but not selection guidance.

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