Skip to main content
Glama

SouthPow crypto & market data

buy_insider_BORR

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

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

Input Schema

NameRequiredDescriptionDefault
limitNoRows, 1-100 (default 20)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior4/5

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

With no annotations, the description carries the full behavioral burden and does disclose the two most decision-relevant traits: it is paid ($0.25 USDC on Base) and requires no account or API key, plus the actual endpoint URL. It does not explain how the USDC payment is transacted (x402 flow, per-call charge on repeat calls), rate limits, or error behavior, which for a paid tool is a meaningful remaining gap.

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 short and front-loaded: cost first, then what the data is, then access requirements and URL. The telegraphic fragments ('Paid.', 'as filed.') are terse but each sentence carries distinct information; nothing is wasted, though the phrasing is slightly clipped for an agent parsing it.

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, annotation-free tool with no output schema, the description covers source, cost, and auth but never describes the shape of the returned rows (transaction date, insider name/role, shares, price, filing link). An agent knows how to call it but not what it will receive, which is a real gap given no output schema exists.

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 a single optional parameter (limit) whose schema description is 100% covered ('Rows, 1-100 (default 20)'). The description adds nothing about paging, ordering, or what a row represents, so the schema baseline of 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?

The description names the specific resource (BORR insider open-market BUYS) and the source (SEC Form 4), including who counts as an insider (officers, directors, 10% owners). That is far more specific than the bare tool name, though it never explicitly contrasts itself with the generic buy_insider sibling or states that it returns a list of filings.

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 by the resource name; there is no 'use this when...' guidance, no mention of when to prefer buy_insider (all-ticker) over buy_insider_BORR, and no note on whether the data is historical-only or includes recent filings. The cost/auth notes help an agent decide to call it, but they are preconditions, not usage routing.

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