Skip to main content
Glama

SouthPow crypto & market data

buy_insider_BBTX

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

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

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 at all, the description carries the full burden and does substantial work: it discloses the cost and payment rail ($0.01 USDC on Base), that no account or API key is needed, the data provenance (SEC Form 4, as filed), and the exact filter (buys only, open-market, insiders). What is missing is the mechanics of the paid call and the row shape, which for a payment-gated endpoint an agent would want to know before calling.

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?

Five terse fragments, front-loaded with the most decision-relevant fact ('Paid') and cost, then scope, then auth, then URL. Every clause earns its place; the only ding is the telegraphic style ('Paid.', 'as filed') which reads as bullet fragments rather than 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 one-optional-parameter read with no output schema, the definition covers the essentials an agent must know before spending money: cost, chain, auth requirements, data source, and the exact row filter. The remaining gap is what a row contains and whether results are paginated or point-in-time, which a caller cannot infer from the schema.

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 coverage is 100% -- the single 'limit' parameter is documented with range 1-100 and default 20 -- so the schema already does the semantic work. The description adds nothing about limit, though nothing is left ambiguous either. Baseline 3 applies when structured fields fully cover the parameter surface.

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 verb and resource: insider BUYS pulled from SEC Form 4 for the single ticker BBTX, with the qualifying rule 'open-market purchases by officers, directors, 10% owners'. The ticker-scoped name plus the sentence make its niche clear against the broader family. It stops short of a 5 because it never names the generic buy_insider sibling to draw the boundary explicitly.

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 implied by purpose -- an agent knows this is the BBTX call as opposed to buy_insider_ANIX or buy_coin_BTC -- and the 'Paid' opener plus '$0.01 USDC on Base' warns that invoking it costs money. But there is no explicit when-to-use/when-not statement and no named alternative for other tickers or for sells-side data.

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