Skip to main content
Glama

SouthPow crypto & market data

buy_insider_CRBG

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

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

Input Schema

NameRequiredDescriptionDefault
limitNoRows, 1-100 (default 20)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations present, the description carries the full behavioral burden, and it does disclose the things that most affect a caller's decision: the payment rail and price, the absence of auth requirements, and the upstream source (SEC Form 4, as filed). It falls short of describing what a response looks like or how many records the default 20-limit window represents, but the cost/auth/source disclosure is substantive rather than decorative.

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 disciplined: the paid/price/auth facts are front-loaded, the data definition follows, and the endpoint URL trails. The URL is arguably redundant since the tool name already encodes the ticker and path, but it is a single low-cost fragment, not padding.

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 single-optional-param read tool with no output schema and no annotations, the description supplies what an agent needs to decide correctly: what the data is, where it comes from, what it costs, and that no credentials are required. The remaining gaps (returned field set, freshness/latency, sort order relative to limit) are real but secondary given there is no output schema to lean on either.

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?

Only one optional parameter (limit) exists and schema description coverage is 100%, so the schema already documents the 1-100 range and default of 20. The description adds no meaning about ordering, whether limit truncates the most recent filings first, or what happens past available rows. Baseline 3 is appropriate when the schema does the heavy lifting.

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 verb-of-acquisition: CRBG insider BUYS from SEC Form 4, scoped to open-market purchases by officers, directors, and 10% owners. That level of specificity (ticker + filing type + transaction type) makes it distinguishable from the generic buy_insider and the many other ticker-named siblings without opening any schema.

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 usage-relevant context a caller needs before invoking: it is paid, costs $0.01 USDC on Base, and requires no account or API key. What it never states is when to prefer this over the generic buy_insider tool or how it relates to the other buy_insider_<TICKER> variants, so selection logic among siblings is left to inference from the name.

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