Skip to main content
Glama

SouthPow crypto & market data

buy_insider_NXG

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

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

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 provided, the description carries the full burden and does well: it discloses the cost and chain, the absence of auth requirements, the data source (SEC Form 4) and the transaction scope (open-market purchases only, excluding other Form 4 event types). It does not cover result freshness, lookback window, or whether the charge is per call versus per row.

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?

Highly front-loaded: the paywall note, the data scope and the price/chain all land in the first two clauses, and the endpoint URL closes it out. The telegraphic 'Paid.' opener is slightly terse but efficient rather than wasteful.

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 single-optional-parameter, no-output-schema endpoint, the description covers the details an agent most needs before spending money: the price, the chain, that no key is required, and the exact data scope. The remaining gap is the time coverage of the filings (how far back and how fresh), which matters for a research-style query.

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%: the single 'limit' parameter is already documented as rows 1-100 with a default of 20. The description adds no further meaning about the parameter, so the baseline of 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 concrete verb and resource: insider BUYS for ticker NXG drawn from SEC Form 4, limited to open-market purchases by officers, directors and 10% owners. That is specific enough to separate it from the buy_coin_*, buy_hn_* and buy_pm_* families. It stops short of explicitly stating that sibling tickers exist under buy_insider_<TICKER> and that only buys (not sales) are covered by this family.

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?

Payment terms ('$0.01 USDC on Base', 'No account, no API key') imply the context in which it is callable, but there is no explicit when-to-use or when-not-to-use guidance and no pointer to the alternative ticker tools. Usage is inferable from the name rather than stated.

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