Skip to main content
Glama

SouthPow crypto & market data

buy_insider_NMCO

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

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

Input Schema

NameRequiredDescriptionDefault
limitNoRows, 1-100 (default 20)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior3/5

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

No annotations exist, so the description carries the full load. It does disclose the critical operational facts: paid at $0.01 USDC on Base, no account or API key needed, and the underlying data being as-filed (unaudited, no restatement). It does not describe the response shape, pagination behavior, data freshness/lag after a Form 4 filing, or whether failed/empty results are still charged.

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?

Four short fragments, front-loaded with the paywall then the data scope then access mechanics. Every clause carries information (cost, chain, auth, endpoint) with no filler.

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, single-endpoint data tool with no output schema and no annotations, the description covers cost, auth, and data provenance but omits the return payload and freshness expectations. That leaves an agent unable to predict what rows it gets for its $0.01.

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 already documents its 1-100 range and default of 20. The description adds no ordering, format, or semantics beyond the schema, so the baseline 3 applies.

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?

Names the exact resource and filter: NMCO insider BUYS sourced from SEC Form 4, restricted to open-market purchases by officers, directors, and 10% owners. This clearly separates it from sibling buy_insider_* tools covering other tickers and from the generic buy_insider tool.

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?

The ticker-specific nature is implied by the description and the tool name, and the payment/auth savings are stated, so an agent can infer context. However, there is no explicit statement of when to pick this over buy_insider (all tickers) or over a sibling ticker tool, and no mention of what happens if the ticker has no filings.

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