Skip to main content
Glama

SouthPow crypto & market data

buy_insider_GRCE

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

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

Input Schema

NameRequiredDescriptionDefault
limitNoRows, 1-100 (default 20)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does well: it discloses the payment rail, price, currency, network, and that no auth is needed, plus the upstream data provenance ('as filed'). It leaves open what happens on payment failure, whether results are cached/fresh, and what the response payload contains.

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-loads the most decision-relevant fact ('Paid.') and then packs source, price, access requirements, and endpoint into a few dense clauses with no filler. Every phrase earns its place.

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 zero-required-param, single-ticker purchase tool with no output schema, the description covers cost, access, data source, and endpoint, which is nearly everything needed to invoke it correctly. It could be more complete about return shape or freshness, but that is a minor gap at this complexity.

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 fully documented in the schema (100% coverage) with range and default, so the description adds nothing beyond it. Per the high-coverage baseline this is adequate rather than enhancing.

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 resource and scope: GRCE insider BUYS sourced from SEC Form 4 open-market purchases by officers, directors and 10% owners. The ticker-specific framing plus the definition of what counts as an insider buy distinguishes it cleanly from the many buy_coin_* and buy_hn_* siblings and from other buy_insider_<TICKER> variants.

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

Usage Guidelines4/5

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

Provides clear operating context: it is a paid call ($0.25 USDC on Base) requiring no account or API key, which lets an agent decide whether the cost is acceptable. It stops short of naming alternatives or exclusions, e.g. pointing to fetch_fact or another ticker tool when GRCE is not the target.

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