Skip to main content
Glama

SouthPow crypto & market data

buy_insider_INM

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

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

Input Schema

NameRequiredDescriptionDefault
limitNoRows, 1-100 (default 20)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

No annotations exist, so the description carries the full burden and does well on the operationally critical parts: it discloses the tool is paid ($0.10 USDC on Base), that no account or API key is needed, and the underlying data source (SEC Form 4, as filed). It does not say what a successful response contains, whether payment is per call, or how fresh the filing data is.

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?

Extremely front-loaded: 'Paid.' is the first word, followed by what the data is, the source, the price, the auth model and the endpoint. Fragments are used deliberately and every clause carries information an agent needs before calling.

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-parameter paid data fetch this covers cost, payment rail, auth requirements, data provenance and the endpoint URL. The remaining gap is return-value shape, which matters somewhat since no output schema is provided, but the core decision inputs are present.

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 coverage is 100% and the single limit parameter is fully documented in the schema (rows, 1-100, default 20). The description adds nothing about limit or pagination behavior, 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?

States a specific verb and resource: insider BUYS for ticker INM sourced from SEC Form 4, with scope narrowed to open-market purchases by officers, directors and 10% owners. The ticker in the name and the description line up, so an agent can distinguish it from the ~50 other buy_insider_<TICKER> siblings, though the description never explicitly says 'for ticker INM' as a scoping statement.

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: the agent infers it should call this when it wants Form 4 insider purchase data for INM. There is no explicit when-to-use, no guidance on choosing between this and the generic buy_insider sibling, and no note on whether historical vs. latest filings are returned.

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