Skip to main content
Glama

SouthPow crypto & market data

buy_insider_STRZ

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

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

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 burden and does reasonably well: it discloses the paid model ($0.05 USDC on Base), that no account or API key is needed, and that data is 'as filed' (implying filing-time freshness rather than real-time). It stops short of describing the response shape or whether payment failure/handling behavior exists.

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 'Paid' and the pricing, then the data definition, then the endpoint URL. Dense and largely waste-free, though the telegraphic phrasing and trailing bare URL read more like a payment manifest than a description.

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 single-parameter, no-output-schema tool, the call mechanics (price, auth, source, filter) are covered, but with no output schema the agent gets no sense of what a row contains, and there is no indication of ordering or whether the result set is a snapshot or history window.

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%, and the single 'limit' parameter is fully documented in the schema with range and default. The description adds no additional meaning about limit behavior or ordering of rows, 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?

States a specific verb+resource: insider BUYS for ticker STRZ sourced from SEC Form 4, restricted to open-market purchases by officers, directors, and 10% owners. The ticker suffix and the 'open-market purchases' qualifier differentiate it from buy_insider and the other buy_insider_* siblings, though it never explicitly says how it relates to the generic 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?

The data filter (Form 4 open-market buys only) implies when the tool is appropriate, and the payment terms imply it is a paid call. But there is no explicit guidance on when to pick this over buy_insider or another ticker variant, and no statement about what it excludes (e.g., insider sales, option exercises).

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