Skip to main content
Glama

SouthPow crypto & market data

buy_insider_DX

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

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

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, the description carries the behavioral burden and does it well: it discloses the paid pricing ($0.10 USDC on Base), the absence of an account or API key, the authoritative source, and the 'as filed' caveat. It does not describe the return shape or pagination behavior, but the payment and auth disclosures are the important context here.

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?

The first word, 'Paid.', puts the cost up front, and the sentences are telegraphic but each carries information. The endpoint URL is somewhat redundant, but the description is otherwise efficient.

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?

The description covers what the agent needs to decide to call it: the source, the pricing, the auth model, and the endpoint. The one gap is that it does not explain what the returned rows look like, which matters because there is no output schema.

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%, so the single limit parameter (rows, 1-100, default 20) is already documented. The description adds no extra meaning about the parameter, so baseline 3 applies because the schema does the work.

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+resource: insider BUYS from SEC Form 4 for ticker DX, scoped to open-market purchases by officers, directors, and 10% owners. It does not explicitly contrast with the generic buy_insider sibling, but the ticker suffix and SEC Form 4 framing let an agent distinguish it.

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 suffix (DX) and the source (SEC Form 4), so an agent can infer this is the per-ticker insider-buy feed. However, there is no explicit guidance on when to pick this over buy_insider or a different ticker sibling.

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