Skip to main content
Glama

SouthPow crypto & market data

buy_insider_BBT

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

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

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 supplied, the description carries the full burden and does well: it discloses that the call is paid ($0.25 USDC on Base), requires no account or API key, and that data comes from SEC Form 4 'as filed'. It stops short of return shape, data freshness/latency, and what happens if payment fails.

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 with the most decision-relevant fact ('Paid'), then data source, then price/chain, then auth and endpoint. Dense and free of filler, though the trailing bare URL is slightly boilerplate rather than descriptive.

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-optional-parameter, no-output-schema tool, the description covers the essentials an agent needs before calling: cost, payment rail, no auth, and data provenance. Missing only return-format expectations and freshness, which are secondary here.

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?

Only one optional parameter (limit) and schema coverage is 100%, so the schema already documents the 1-100 range and default of 20. The description adds nothing about ordering, filtering, or what a row represents, so 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?

Names a specific verb and resource: open-market insider BUYS for ticker BBT sourced from SEC Form 4, with the filer categories spelled out (officers, directors, 10% owners). The embedded ticker and URL make it distinguishable from the ~50 other buy_insider_* siblings, though it never explains how it relates to the aggregate buy_insider tool.

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 this returns insider purchase activity for BBT. There is no explicit when-to-use / when-not-to-use statement, no mention of the buy_insider aggregate sibling or the buy_coin_BBT-adjacent tools, and no guidance on choosing between them.

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