Skip to main content
Glama

SouthPow crypto & market data

buy_insider_DLPN

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

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

Input Schema

NameRequiredDescriptionDefault
limitNoRows, 1-100 (default 20)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description does well on the access and cost model: pay-per-call price, payment chain/asset, and no authentication. It says nothing about latency, data freshness, pagination, or what happens on payment failure, which are the behaviors an agent most needs to plan around for a paid call.

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?

Compact and front-loaded, leading with 'Paid.' before the data scope and endpoint. The URL is arguably redundant with the tool's transport but is a single token of cost.

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, schema-only tool with no output schema, the description never sketches the shape of the returned rows (fields, ordering, whether the filing link or transaction date is included). An agent knows what it is buying but not precisely what it receives.

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% and the single 'limit' parameter (rows 1-100, default 20) is fully documented in the schema. The description adds no guidance on limit usage or ordering, so 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 verb and resource: insider BUYS for ticker DLPN from SEC Form 4, restricted to open-market purchases by officers, directors and 10% owners. The ticker is embedded in the name, so the description's added value is the data source and transaction type rather than sibling differentiation.

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?

It signals that the call is paid ($0.10 USDC on Base) and needs no account or API key, which are real usage constraints. It never says when to prefer this over the generic buy_insider tool or over sibling ticker variants, so the routing decision is left implicit.

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