Skip to main content
Glama

SouthPow crypto & market data

buy_insider_JCTC

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

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

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, the description carries the full behavioral burden and does disclose the key traits: it is a paid endpoint, the exact price and chain, and that no account or API key is required. It stops short of describing the response shape, pagination, or what happens on payment failure, and 'as filed' hints at data freshness without stating it explicitly.

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 telegraphic fragments with zero filler, front-loading the payment requirement before the data description and price. It is efficient but slightly staccato ('Paid.' as a standalone fragment) and the endpoint URL is arguably redundant with the tool's own wiring.

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-parameter paid data endpoint with no output schema, the description covers cost, chain, auth model, data source and transaction filter — enough for an agent to decide and invoke correctly. The remaining gap is the return format and how many rows/pages to expect, which matters for an agent budgeting a paid call.

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 parameter (limit) and schema description coverage is 100%, so the schema already explains 'Rows, 1-100 (default 20)'. The description adds nothing about it — no note on ordering, what a row represents, or whether the cap truncates results — so the baseline of 3 applies.

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: JCTC insider BUYS from SEC Form 4, restricted to open-market purchases by officers, directors and 10% owners, 'as filed'. That distinguishes it both from the generic buy_insider sibling and from the hundreds of buy_coin_* tools, which return price data rather than filings.

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?

Usage is implied by the data description (call this to get JCTC insider buy filings) and the prerequisites are spelled out ($0.01 USDC on Base, no account, no API key). However, there is no explicit when-to-use/when-not guidance relative to buy_insider (the un-tickered sibling), and no statement that sells or other Form 4 transaction types are excluded from the result set.

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