Skip to main content
Glama

SouthPow crypto & market data

buy_insider_DSM

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

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

Input Schema

NameRequiredDescriptionDefault
limitNoRows, 1-100 (default 20)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

No annotations are supplied, so the description carries the behavioral burden — and it does a good job: it discloses that the call costs $0.01 USDC on Base, requires no account or API key, and is sourced from SEC Form 4 as filed. Remaining gaps are failure modes (insufficient payment, rate limits) and whether the data is delayed.

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?

Dense, front-loaded and free of filler: cost, data source, scope, auth requirements, and endpoint are all in four short sentences. The telegraphic fragment style and the raw URL are slightly scruffy but each element carries information.

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-parameter, no-required-args data fetch, the description covers source, scope, price, and authentication adequately, and there is no output schema to explain. What is missing is minor: response shape hints and payment-failure behavior.

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?

Only one optional parameter exists and the schema already documents it fully ('Rows, 1-100 (default 20)'), giving 100% coverage. The description adds nothing about limit behavior such as ordering or what a row contains, so baseline 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 resource (DSM insider buys from SEC Form 4) and narrows the scope to open-market purchases by officers, directors, and 10% owners. The ticker in the name plus the description makes it distinguishable from the generic buy_insider and the other ticker-specific variants without opening any schema.

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?

The per-ticker scoping is implied by the name and the 'DSM' in the description, and the 'Paid / $0.01 USDC' sentence is a useful decision input. However, with roughly 280 sibling tools, there is no explicit statement of when to use this versus buy_insider (generic) or how to pick the right ticker-specific variant.

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