Skip to main content
Glama

SouthPow crypto & market data

buy_insider_ANIX

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

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

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 carries the full burden and does well: it discloses that the call is paid ($0.01 USDC on Base), that no account or API key is needed, and that data is 'as filed' from SEC Form 4. It does not explain how the payment is executed (e.g. x402 handshake) or what happens when no purchases exist for the ticker, which are the remaining behavioral gaps.

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?

Four short fragments, with the most decision-relevant fact ('Paid') front-loaded, followed by what the data is, the price/chain, the auth requirement, and the endpoint. No sentence is wasted.

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-parameter read tool with no output schema, the description covers source, scope, cost, and auth adequately. The main omission is any hint about the shape or ordering of returned rows, but the SEC Form 4 provenance makes the return content largely predictable.

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 parameter and the schema documents it fully ('Rows, 1-100 (default 20)'), so schema coverage is 100% and the baseline of 3 applies. The description adds nothing about the limit parameter, such as ordering or whether it caps the most recent filings.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('ANIX insider BUYS'), the exact data source (SEC Form 4) and the covered filer classes (officers, directors, 10% owners), plus the scope limit of open-market purchases only. This cleanly separates it from buy_coin_ANIX (price data) and from the generic buy_insider sibling that presumably spans all tickers.

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 is only implied: an agent can infer this returns insider purchase filings for ANIX specifically. There is no explicit when-to-use or when-not guidance, and neither the generic buy_insider nor the same-ticker buy_coin_ANIX is named as an alternative for a different question (all-ticker insider flow vs. price data).

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