Skip to main content
Glama

SouthPow crypto & market data

buy_insider_GROW

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

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

Input Schema

NameRequiredDescriptionDefault
limitNoRows, 1-100 (default 20)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/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 that the call is paid ($0.10 USDC on Base), that no credentials are required, the upstream source (SEC Form 4), and the filter applied (open-market purchases only, excluding other transaction types). It omits what an empty or failed response looks like and whether the payment settles before or after the query, which keeps it from a 5.

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-loads the paywall status and the resource, then tacks on cost, auth, and endpoint in compact fragments with no filler. Slightly telegraphic ('as filed', the bare URL) but every clause carries information an agent needs before spending money.

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 one-parameter, no-output-schema paid lookup, the description covers cost, payment rail, authentication model, data provenance, and endpoint. The main gap is the shape of the returned records (which Form 4 fields come back), which matters when the agent is paying per call and cannot preview the result.

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 already documented as rows 1-100 with a default of 20. The description adds nothing about paging, ordering, or what a row contains, so it earns the baseline 3 for a fully described schema.

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 verb+resource (insider BUYS) and a precise data source (SEC Form 4 open-market purchases by officers, directors, 10% owners) scoped to the GROW ticker. The ticker suffix in the name is confirmed by the description. It does not explicitly say how it differs from the generic sibling buy_insider or from other buy_insider_<TICKER> variants, so it stops short of full sibling differentiation.

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 description gives useful preconditions for using it (paid, no account or API key needed) but never states when an agent should choose this tool over buy_insider or another per-ticker sibling, nor what to do if no Form 4 purchases exist. Usage is implied by the ticker scope rather than explained.

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