Skip to main content
Glama

SouthPow crypto & market data

buy_insider_PCQ

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

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

Input Schema

NameRequiredDescriptionDefault
limitNoRows, 1-100 (default 20)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations present, the description carries the full burden, and it does disclose real behavioral facts: the call is paid ($0.10 USDC on Base), requires no account or API key, and returns data exactly as filed with the SEC. It omits what happens on failed payment, freshness/latency of the data, ordering, and whether the purchase is a one-time unlock or per-call charge — meaningful gaps for a paid tool.

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?

The critical qualifier 'Paid' is front-loaded, followed by data source, scope, price, auth model and endpoint — dense and free of padding. The telegraphic style ('Paid.', 'No account, no API key.') is terse and slightly fragmented, and 'PCQ' is never identified as a ticker symbol.

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 one-parameter, no-annotations, no-output-schema paid endpoint, the description covers cost, authentication and data provenance, which is the essential minimum. It stops short of describing the shape of returned rows (insider name, role, shares, price, filing date) or recency, leaving the agent unable to judge what it is actually buying.

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 parameter, `limit`, and schema description coverage is 100% ('Rows, 1-100 (default 20)'), so the schema already fully documents it. The description adds nothing about `limit` — no note on maximum sensible values or how ordering interacts with the row cap. Baseline 3 applies when the schema does the work.

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 states a specific resource and scope: insider BUYS for ticker PCQ sourced from SEC Form 4, restricted to open-market purchases by officers, directors and 10% owners. That is far more precise than the bare name. It does not, however, distinguish itself from the generic sibling `buy_insider`, which presumably returns the same data across all tickers, so an agent must infer that this is the ticker-scoped variant.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no explicit when-to-use or when-not guidance. Nothing tells the agent to prefer `buy_insider` for multi-ticker or discovery queries and this tool for a known ticker, nor whether it pulls only the latest filings or a full history. The usage context is only implied by the ticker suffix.

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