Skip to main content
Glama

SouthPow crypto & market data

buy_insider_LCU

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

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

Input Schema

NameRequiredDescriptionDefault
limitNoRows, 1-100 (default 20)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations at all, the description carries the full behavioral burden and does well on the dimensions that matter most: it discloses the payment model, price, chain, and that no account or API key is required. It omits what the response looks like, whether a failed or empty query still costs $0.01, and any rate/retry behavior.

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 terse clauses, front-loaded with the most decision-relevant fact ('Paid'), then the data semantics, then price/auth, then the endpoint. Nothing is padded and nothing needs reordering.

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?

For a paid, single-parameter fetch with no output schema and no annotations, the description covers source, cost and auth but leaves the agent guessing about the return payload and the payment flow (e.g. is the URL an x402 endpoint requiring a 402-then-pay handshake?). Adequate, but a paid tool warrants more detail about what the caller receives for their money.

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 parameter and the schema already documents it fully ('Rows, 1-100 (default 20)'), so baseline 3 applies. The description adds no meaning beyond that, such as whether limit applies to filings or transactions, or what the default ordering is.

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: LCU insider open-market BUYS from SEC Form 4, limited to officers, directors and 10% owners. That scope narrowing (purchases only, not sales or derivative filings) genuinely distinguishes it from a generic insider-filings tool, though it never explicitly contrasts itself with the sibling buy_insider or other buy_insider_<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?

Usage is implied by the ticker-specific name and the data source, and the 'Paid... $0.01 USDC on Base' clause usefully flags a cost gate before invocation. However there is no explicit when-to-use guidance, no mention of when to prefer the generic buy_insider tool, and no note about what to do if the caller has no Base USDC balance.

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