Skip to main content
Glama

SouthPow crypto & market data

buy_insider_IMSR

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

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

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 supplied, the description carries the burden and does substantial work: it discloses the payment model ($0.25 USDC on Base), that no account or API key is required, and that only open-market BUYS are returned 'as filed' — so the agent knows sales and derivative transactions are excluded. Gaps remain on rate limits, pagination, and the exact response shape.

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?

Four short clauses, front-loaded with the most decision-relevant fact ('Paid'), then data scope, then price, then access requirements. Efficient and scannable; the raw endpoint URL is arguably redundant for an agent that invokes the tool by name.

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 paid data endpoint with no output schema, the description covers cost, auth, source, and record scope — the things an agent must know before spending money. The one meaningful omission is what the returned rows contain, which matters since no output schema is defined.

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 (limit) with 100% schema description coverage, so the schema already documents the 1-100 range and default of 20. The description adds nothing about it, which is acceptable at full coverage but not more than baseline.

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 (IMSR insider buys) and a precise source and scope: SEC Form 4 open-market purchases by officers, directors and 10% owners. The ticker suffix makes it distinguishable from the other ~90 buy_insider_* siblings, though it never says explicitly that the family is ticker-partitioned.

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 'Paid' opener and the price imply this is a deliberate, metered fetch rather than a casual lookup, and the ticker in the name implies IMSR-specific usage. However, it never states when to use this versus the generic buy_insider tool or another ticker variant, and gives no guidance on skipping it when the symbol is not of interest.

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