Skip to main content
Glama

SouthPow crypto & market data

buy_insider_NBIS

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

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

Input Schema

NameRequiredDescriptionDefault
limitNoRows, 1-100 (default 20)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full behavioral burden and does well: it discloses that the call is paid, the exact cost ($0.01 USDC on Base), that no account or API key is needed, and the underlying data provenance (SEC Form 4, open-market purchases only, as filed). It omits whether the charge applies per call including empty results, and gives no sense of response latency or result shape.

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?

Four short fragments, front-loaded with the most decision-relevant fact ('Paid') and the price before the endpoint URL. Every element carries information, though the telegraphic style ('Paid.', 'as filed.') costs a little readability versus a single well-formed sentence.

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 paid data-fetch tool with no output schema and no annotations, the description covers access mechanics (price, chain, auth) and data provenance well. It stops short of describing the returned fields or how to interpret an empty/error result, which matters more here because each invocation costs money.

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 the schema already does the work. The description adds nothing about the limit, not even that it caps row count against a costed call. Baseline 3 applies given 100% schema coverage.

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 resource and scope: NBIS insider BUYS from SEC Form 4, restricted to open-market purchases by officers, directors, and 10% owners. That scope detail distinguishes it from a generic insider tool that would include sales and option exercises. It does not name a sibling to route away to (e.g., the generic buy_insider), which keeps it just under a 5.

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?

Leading with 'Paid' plus the exact price and payment rail implicitly tells the agent this is a costed call rather than a free read, which is useful context. However, it never states when to choose this over buy_insider (all-ticker version) or what to do if the ticker has no Form 4 buys, leaving selection to inference.

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