Skip to main content
Glama

SouthPow crypto & market data

buy_insider_NPB

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

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

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 disclose the important non-obvious traits: paid ($0.05 USDC on Base), no account or API key required, and that the data is as-filed SEC Form 4. It omits return shape, pagination beyond limit, and data freshness.

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?

Three short fragments, zero filler. Cost and payment details are front-loaded before the data-source explanation, which is the right ordering for a paid tool.

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 data fetch with no output schema, the description covers everything an agent must know before spending money: price, rail, auth requirements, endpoint, and dataset definition. Freshness and response format are the only meaningful gaps.

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 limit parameter is already fully described in the schema (rows, 1-100, default 20), so the description adds no meaning beyond it. Baseline 3 applies at 100% schema coverage.

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 (BUYS), a specific ticker scope (NPB), and the precise data source and filter (SEC Form 4 open-market purchases by officers, directors, 10% owners). It is immediately distinguishable from the many buy_coin_* and buy_pm_* siblings.

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?

Signals this is a paid call with a stated price and payment rail, which is a real usage prerequisite, but never says when an agent should prefer this over buy_insider_NBIS-style siblings or the generic buy_insider, nor when not to call it.

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