Skip to main content
Glama

SouthPow crypto & market data

buy_insider_KWY

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

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

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, the description carries the full burden and does well: it discloses that the call is paid ($0.01 USDC on Base), requires no account or API key, and that data is limited to open-market purchases 'as filed'. It does not say whether data is real-time or delayed, or what the response looks like, which keeps it below a 5.

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?

Four short, front-loaded fragments with no filler; the cost notice comes first and the data scope second. The bare URL token at the end is slightly telegraphic but functional.

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-param tool with no output schema, the description covers cost, payment rail, access requirements, and the exact data scope. The main remaining gap is return-value shape, which matters here since no output schema exists to explain it.

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 optional 'limit' parameter with 100% schema description coverage, so the schema already explains range and default. The description adds nothing about paging, cost scaling with row count, or ordering of results, 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 resource and dataset: KWY insider BUYS sourced from SEC Form 4, explicitly limited to open-market purchases by officers, directors and 10% owners. That scope statement separates it from the large buy_insider_* family and from buy_coin_KWY, though it never names a sibling or the generic buy_insider parent tool directly.

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 context is implied rather than stated: an agent can infer 'call this to get insider buying for KWY', and the pricing/access notes tell it what to expect. There is no explicit when-to-use versus buy_insider (all tickers) or buy_coin_KWY, and no exclusion of cases like insider sales or options 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