Skip to main content
Glama

SouthPow crypto & market data

buy_insider_LRN

Paid. LRN insider BUYS from SEC Form 4 (open-market purchases by officers, directors, 10% owners), as filed. $0.25 USDC on Base. No account, no API key. URL https://southpow.media/v1/insider-buys/LRN.

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

Input Schema

NameRequiredDescriptionDefault
limitNoRows, 1-100 (default 20)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/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 disclosure burden and does a solid job: it names the data source (SEC Form 4), the exact filter (insider open-market purchases only), the pricing and payment chain, and that no auth is required. It stops short of describing the payment mechanism itself (e.g., how the $0.25 USDC charge is settled) and any rate limits or failure modes.

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?

Front-loaded with 'Paid' and the core data definition, then payment terms, then the endpoint — a sensible ordering for an agent deciding whether to call. It is written in dense fragments that are efficient, though the trailing bare URL reads as machine plumbing rather than guidance.

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, so the description should ideally sketch the shape of returned rows (filer, role, shares, price, date) and how payment is executed. Payment cost and auth are covered, but the return payload and settlement flow remain undocumented for a tool with a paid, non-trivial call path.

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 one optional parameter (limit) and the schema description coverage is 100%, with 'Rows, 1-100 (default 20)' already documenting range and default. The description adds no further meaning about ordering, what a row contains, or whether the limit truncates a larger result set, so the baseline 3 applies.

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 resource and scope: 'LRN insider BUYS from SEC Form 4 (open-market purchases by officers, directors, 10% owners)'. That verb-plus-resource plus the explicit filter (buys only, open-market only) tells an agent exactly what data comes back. It does not explicitly say how it differs from the generic sibling 'buy_insider', but the ticker scope is embedded in the resource name.

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 prerequisites are stated well — paid, $0.25 USDC on Base, no account, no API key — which is genuinely useful gating information. However, there is no when-to-use vs. alternatives guidance: it never says whether to prefer this ticker-specific tool over the generic 'buy_insider' or how it relates to 'buy_coin_LRN', so routing must be inferred 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