Skip to main content
Glama

SouthPow crypto & market data

buy_insider_CHCO

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

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

Input Schema

NameRequiredDescriptionDefault
limitNoRows, 1-100 (default 20)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior4/5

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

With zero annotations, the description carries the full burden and does reasonably well: it discloses the data provenance (SEC Form 4), the exact scope (open-market purchases only, excluding grants, exercises, and sales), the cost and payment chain ($0.01 USDC on Base), the absence of auth requirements, and the literal endpoint URL. Gaps remain on recency/time coverage and what the rows contain, but the behavioral profile is unusually well specified for an unannotated tool.

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?

Telegraphic but front-loaded: 'Paid.' immediately flags the metered nature, followed by scope, cost, auth, and endpoint in that order. Every fragment carries information; no filler. The style is terse to the point of being staccato, but readability is not harmed.

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, unannotated, no-output-schema tool, the definition covers what, cost, auth, and source, which is a lot. It still leaves out how far back the filings go, whether results are latest-first, and what a row contains — details the agent cannot recover from the schema or annotations, which are absent.

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 with range and default, so the schema does the work. The description adds nothing about the limit and, notably, says nothing about how the returned rows are ordered or bounded in time, which matters more than the limit itself.

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 action: CHCO insider open-market BUYS sourced from SEC Form 4, naming who counts as an insider (officers, directors, 10% owners). The ticker is explicit, which separates it from the generic buy_insider and the other buy_insider_XXX siblings, though it never says in words 'this is the CHCO-specific variant, use buy_insider for other tickers.'

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?

Prerequisites are clear ('No account, no API key', $0.01 USDC on Base, direct URL), which tells the agent it can call this without setup. However, there is no explicit when-to-use statement and no routing to alternatives — nothing says to prefer buy_insider (the generic multi-ticker tool) when the ticker is unknown, or that this dataset covers buys only and a different tool is needed for sells.

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