Skip to main content
Glama

SouthPow crypto & market data

buy_insider_TRTX

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

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

Input Schema

NameRequiredDescriptionDefault
limitNoRows, 1-100 (default 20)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/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 burden and does well: it discloses a paid model with the exact price and chain, that no account or API key is required, that the data is SEC Form 4 as filed, and that only open-market purchases (not sales or derivative exercises) are included. It stops short of describing the response shape or whether results are paginated or ranked by date.

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?

Four short, front-loaded fragments: payment model first, then scope and source, then price/chain, then access requirements and endpoint. No filler and nothing buried.

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 read tool with no output schema, the definition covers cost, access, source, and semantic scope, which is most of what an agent needs to decide and call. The remaining gap is the absence of any hint about what a returned row contains or the date span covered.

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?

There is a single optional `limit` parameter whose schema description is fully documented at 100% coverage (rows 1-100, default 20). The description adds nothing about row ordering, date window, or what a row contains, so the schema does all the work — baseline 3.

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 and resource: buying TRTX insider BUY records sourced from SEC Form 4, restricted to open-market purchases by officers, directors and 10% owners. The ticker suffix and the data-source detail distinguish it from the generic buy_insider sibling, but the description never explicitly says the unsuffixed tool covers 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?

Usage is implied: if you want TRTX insider-buy data, call this. There is no explicit when-to-use / when-not-to-use statement and no comparison to the buy_insider or buy_coin siblings, though 'Paid. ... $0.10 USDC on Base' gives an agent the practical gating fact it needs before invoking.

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