Skip to main content
Glama

SouthPow crypto & market data

buy_insider_BZUN

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

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

Input Schema

NameRequiredDescriptionDefault
limitNoRows, 1-100 (default 20)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

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

With no annotations, the description usefully discloses the $0.05 USDC price, Base payment network, lack of account or API-key requirements, and the as-filed SEC data provenance. It does not describe payment mechanics, data freshness, or whether the operation is strictly read-only apart from payment.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is compact and front-loads both the paid nature and the precise data scope. Cost, authentication requirements, and endpoint URL each add practical information without substantial redundancy.

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 simple one-parameter endpoint, the ticker, filing scope, source, price, network, authentication requirements, and URL provide enough context for selection and basic invocation. Because there is no output schema, brief details about response structure, ordering, or freshness would improve completeness, and the payment flow remains unspecified.

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?

The schema fully documents the sole optional limit parameter, including its 1-100 range and default of 20. The description adds no parameter guidance, so the fully covered schema appropriately carries that burden.

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 identifies the exact resource and scope: BZUN open-market insider purchases reported on SEC Form 4 by officers, directors, and 10% owners. It makes clear that this is a fixed-ticker data product, though an explicit retrieval verb and differentiation from generic buy_insider would make selection even clearer.

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

Usage Guidelines4/5

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

An agent can readily select it when BZUN insider-buying filings are needed, based on the ticker, transaction type, and source. It does not explain when to use buy_insider instead or note exclusions such as insider sales and non-open-market transactions beyond the parenthetical 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