Skip to main content
Glama

SouthPow crypto & market data

buy_insider_GRX

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

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

Input Schema

NameRequiredDescriptionDefault
limitNoRows, 1-100 (default 20)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/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 well: it discloses that the call is paid ($0.05 USDC on Base), that no account or API key is needed, and names the upstream data source and endpoint. It omits what a paid call actually returns (fields, row shape) and whether payment is settled per call, which matters for an agent deciding to spend.

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 paid marker and the data definition, with no filler. The raw URL is useful for verification but slightly crowds out functional detail.

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-parameter data tool with no output schema and no annotations, the description covers cost, auth, and provenance but not the return payload or freshness/latency. An agent knows how to call it and what it costs, but not exactly what it receives.

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 description coverage is 100% and the single 'limit' parameter is fully documented in the schema (rows, 1-100, default 20). The description adds nothing about it, 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?

States a specific resource and scope: GRX insider BUYS sourced from SEC Form 4, with the qualifying definition (open-market purchases by officers, directors, 10% owners). That is far more than a restatement of the name. It does not explicitly frame itself as the GRX-specific variant of the buy_insider family, so sibling differentiation rests on the ticker embedded in the name and URL.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use guidance and no routing to alternatives, despite dozens of sibling tools including a generic buy_insider and per-ticker variants. The agent must infer that this returns only GRX data and that other tickers require other tools. The 'Paid' marker signals a purchase context but does not say when paying is warranted.

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