Skip to main content
Glama

SouthPow crypto & market data

buy_insider_GOLD

Paid. GOLD insider BUYS from SEC Form 4 (open-market purchases by officers, directors, 10% owners), as filed. $0.10 USDC on Base. No account, no API key. URL https://southpow.media/v1/insider-buys/GOLD.

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

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?

No annotations exist, so the description carries the full burden. It does disclose the two things an agent most needs here: that the call costs $0.10 USDC on Base and that no auth is required. It says nothing about what happens on payment failure, response shape, sort order, freshness, or whether repeated calls re-charge.

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?

Front-loaded with the critical facts (paid, what data, price, no auth) in five short clauses with zero filler. The telegraphic style is slightly choppy, but every clause 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-parameter paid data feed with no output schema, the description covers source, cost, auth and endpoint, which is the essential core. It leaves out what a returned row contains and how recent the filings are, gaps an agent would notice when interpreting results.

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 schema coverage is 100%. The description adds no further meaning about the limit, which is acceptable at baseline but not additive.

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?

The description names a specific resource (GOLD insider open-market BUYS from SEC Form 4) and scopes it precisely to purchases by officers, directors and 10% owners. The uppercase BUYS plus the 'as filed' qualifier make it distinguishable from a generic insider or sell-side variant.

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?

It states the commercial terms (paid, $0.10 USDC on Base, no account or API key) and gives a concrete endpoint URL, which implies usage context. However, it never says when to pick this over the sibling buy_insider generic tool or when not to use it (e.g. for other tickers, or for insider sales).

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