Skip to main content
Glama

SouthPow crypto & market data

buy_insider_NVA

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

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

Input Schema

NameRequiredDescriptionDefault
limitNoRows, 1-100 (default 20)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior3/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 disclose the key operational traits: it is a paid call ($0.05 USDC on Base), requires no authentication, and pulls data 'as filed' from SEC Form 4. It omits what happens on payment failure, whether results are live or cached, rate limits, and the response shape, which are meaningful gaps for a metered endpoint.

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?

The description is front-loaded with 'Paid.' and then packs source, cost, auth requirements, and endpoint into a few dense clauses with no filler. Slightly fragmentary telegraphic style, but every phrase carries information.

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 one-optional-parameter tool with no output schema and no annotations, the description covers cost, access, and data source well enough to invoke it. It does not describe what a returned row contains, which is left entirely unspecified since no output schema exists.

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 single optional 'limit' parameter is fully documented in the schema (rows 1-100, default 20), so schema coverage is 100% and the baseline applies. The description adds no meaning beyond that, such as ordering of rows or what a limit of 100 truncates.

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 (NVA insider buys from SEC Form 4), narrows the data to open-market purchases by officers, directors, and 10% owners, and clarifies that 'buy' means purchasing the data feed, not a trading action. The ticker in the tool name plus the explicit NVA scope makes it distinguishable from the many buy_insider_* siblings. It stops just short of naming the unfiltered sibling (buy_insider) as the alternative.

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?

Prerequisites are stated clearly ('No account, no API key'), and the price is given up front, which tells an agent what it must be able to spend. There is no explicit when-to-use/when-not guidance, and it never mentions the generic buy_insider tool for other tickers or the sibling insider tools, so routing is only implied by the ticker suffix.

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