Skip to main content
Glama

SouthPow crypto & market data

buy_insider_ZONE

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

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

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 supplied, the description carries the full disclosure burden. It does useful work: it declares a paywall with a concrete price and chain, states that no account or API key is needed, and scopes the data to open-market purchases only (implicitly excluding sales, option exercises, and gifts). It says nothing about data freshness relative to the filing, rate limits, or what happens on payment failure.

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 fragments, with the most decision-relevant fact ('Paid') front-loaded and the data provenance immediately after. The raw endpoint URL is arguably dead weight since the agent invokes the tool rather than fetching it, but nothing else is padded.

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, paywalled endpoint, the description covers cost, authentication, and data provenance, which is the core. It leaves gaps an agent would care about at call time: the shape of returned rows, how stale the data is versus the Form 4 filing date, and whether repeated calls incur repeated charges.

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 description coverage is 100% and the single `limit` parameter already documents its range and default ('Rows, 1-100 (default 20)'). The description adds no meaning about ordering, what a row represents, or how limit interacts with pagination, so the 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?

The description names a specific resource and verb: insider BUYS for ticker ZONE drawn from SEC Form 4 open-market purchases by officers, directors, and 10% owners. The ticker suffix and the parenthetical definition of what counts as an insider buy let an agent distinguish this from buy_coin_ZONE or buy_pm_* siblings. It stops short of explicitly contrasting itself with the generic buy_insider tool, which presumably takes a ticker argument.

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?

The only guidance is commercial ('Paid', '$0.01 USDC on Base', 'No account, no API key'), which tells the agent how to pay but not when to choose this tool over buy_insider or a different ticker variant. No exclusions, no mention of freshness windows, and no statement of what an agent gains from the per-ticker variant rather than the generic one.

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