Skip to main content
Glama

SouthPow crypto & market data

buy_insider_SNES

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

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

Input Schema

NameRequiredDescriptionDefault
limitNoRows, 1-100 (default 20)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/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 important behavioral facts: the call costs $0.01 USDC on Base, requires no account or API key, and returns only buy-side Form 4 filings (not sales). It does not describe the response shape, recency window, or what happens if payment fails, and "as filed" is vague about latency and completeness.

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?

Front-loaded with the critical constraint ("Paid.") followed by scope, cost, auth model, and endpoint URL in a handful of clauses. No filler and nothing buried; each fragment carries information.

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-parameter, no-output-schema read tool, the description covers source, filtering, cost, and auth requirements, which is most of what an agent needs. The remaining gap is that the return format is undocumented and there is no output schema to compensate.

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?

Only one parameter (limit) exists and the schema already documents it at 100% coverage, including the 1-100 range and default of 20. The description adds no meaning about how row limiting interacts with the dataset or ordering, so baseline 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?

The description names a specific verb and resource: insider BUYS for ticker SNES sourced from SEC Form 4, explicitly limited to open-market purchases by officers, directors, and 10% owners. That is far more precise than the sibling pattern (buy_insider_<TICKER>, buy_coin_<TICKER>) would imply on its own, though it never explicitly says how it relates to the generic buy_insider or to the per-ticker 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?

Usage context is implied through the payment prerequisites ("Paid. $0.01 USDC on Base. No account, no API key."), which tells an agent what is needed before calling. There is no explicit when-to-use versus buy_insider or buy_coin_* guidance, and no statement of when not to use it or whether other tickers require a different tool.

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