Skip to main content
Glama

SouthPow crypto & market data

buy_insider_FFIN

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

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

Input Schema

NameRequiredDescriptionDefault
limitNoRows, 1-100 (default 20)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does well: it discloses the paywall ($0.10 USDC on Base), that no account or API key is needed, the upstream source (SEC Form 4, as filed), and the exact event filter. It does not describe response shape, row fields, data freshness, or whether each call incurs the charge versus a session.

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?

Front-loads the paid nature in one word, then the data definition, then price/chain, then access requirements, then endpoint. No filler and no redundancy across the two sentences.

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-parameter, no-output-schema data purchase tool, the essential facts — cost, payment chain, auth requirements, source, and filter semantics — are all present. The remaining gap is what the returned rows contain, which matters more here since no output schema exists.

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 optional 'limit' parameter is documented there as rows 1-100 with a default of 20. The description adds nothing about the parameter, 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 action and resource: FFIN insider BUYS sourced from SEC Form 4, scoped to open-market purchases by officers, directors, and 10% owners. The parenthetical defines the exact filter, which cleanly separates this from the generic buy_insider sibling and from the many other ticker-specific buy_insider_* tools.

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 ticker in the name rather than stated: an agent can infer this returns Form 4 buy data for FFIN only. There is no explicit guidance on when to pick this over buy_insider (the aggregate) or a sibling ticker, and no exclusions such as 'buy_insider_FFIN covers only purchases, not sales'.

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