Skip to main content
Glama

SouthPow crypto & market data

buy_insider_STC

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

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

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 behavioral burden and does a decent job: it discloses that the call is paid, the exact price and settlement (USDC on Base), that no account or API key is required, the upstream data source (SEC Form 4, as filed) and the direct endpoint URL. It does not cover what happens on payment failure, freshness/lag of the filing data, or how many rows come back by default beyond the schema.

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?

Extremely front-loaded and waste-free: cost first, then data scope, then payment mechanics, then endpoint. The telegraphic style ('Paid.', 'as filed') is efficient, though the abbreviation of the ticker and the terse fragments slightly reduce clarity for an agent unfamiliar with the venue.

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, no-output-schema, no-annotation data tool, the description supplies the pieces an agent most needs: what the data is, where it comes from, and exactly what it costs to call. Remaining gaps (response shape, data latency) are modest given the tool's simplicity and the absence of an output 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?

There is only one parameter (limit) and schema description coverage is 100%, so the schema already documents the 1-100 range and default of 20. The description adds nothing about limit behavior, so the 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 a specific verb and resource: insider open-market BUYS for ticker STC, sourced from SEC Form 4, with the filer classes (officers, directors, 10% owners) spelled out. That distinguishes it from the generic buy_insider tool and from the many buy_coin_* siblings. It stops short of explicitly telling an agent to use a different buy_insider_<TICKER> sibling for other symbols, leaving that routing to inference from the name.

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 and access prerequisites ($0.05 USDC on Base, no account, no API key) are given up front, which helps an agent decide whether it can call this at all. However, there is no explicit when-to-use guidance against alternatives such as buy_search or the other buy_insider_* tools, so the usage context is only implied by the ticker suffix and the 'insider buys' scope.

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