Skip to main content
Glama

SouthPow crypto & market data

buy_insider_GF

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

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

Input Schema

NameRequiredDescriptionDefault
limitNoRows, 1-100 (default 20)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose cost ($0.10 USDC on Base), the absence of auth requirements, the upstream source, and that only open-market purchases are included. It says nothing about the return shape, ordering, or what happens on payment failure, which are material for a paid fetch.

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?

Six telegraphic fragments, front-loaded with the paid flag and the core definition, then cost, auth, and endpoint. No filler, though the fragment style makes the source scoping read as a run-on parenthetical.

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?

There is no output schema and no annotations, so the description is the only documentation an agent gets; it covers source, scope, cost, and URL but leaves the returned record structure and row semantics undefined for what is a paid data pull.

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 coverage is 100% with a single 'limit' parameter already documented as rows 1-100 with a default of 20. The description adds no detail about what a row contains or how limit interacts with the fixed ticker, so baseline 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 verb and resource: insider BUYS for ticker GF sourced from SEC Form 4, scoped to open-market purchases by officers, directors, and 10% owners. The 'as filed' qualifier and the ticker suffix let an agent distinguish it from the sibling ticker variants.

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 tells the agent this is a paid call with a price and payment rail, which is useful gating information, but it never states when to pick this over the generic 'buy_insider' tool or the many other ticker variants. Usage is implied by the ticker in the name 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