Skip to main content
Glama

SouthPow crypto & market data

buy_insider_RENT

Paid. RENT insider BUYS from SEC Form 4 (open-market purchases by officers, directors, 10% owners), as filed. $0.05 USDC on Base. No account, no API key. URL https://southpow.media/v1/insider-buys/RENT.

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

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 carries the full burden and does disclose the most consequential traits: it is a paid call ($0.05 USDC on Base), requires no account or API key, and exposes the endpoint URL. It is silent on the historical window covered, response shape, pagination, and what happens when payment is absent or fails, which are material for a paid endpoint.

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?

Five short fragments with the cost and ticker front-loaded, so the highest-value facts land first and nothing is wasted. The telegraphic style and unusual capitalization ('insider BUYS') read as slightly noisy but do not obscure meaning.

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 one-parameter read tool with no output schema, the description should convey what a returned row looks like and how far back it goes; neither is present. Payment and access requirements are covered well, which keeps it at an adequate rather than inadequate level.

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 parameter (limit) exists and the schema documents it fully ('Rows, 1-100 (default 20)'), so coverage is 100% and the baseline is 3. The description adds no extra meaning about what a row contains or how limit interacts with the underlying data volume.

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?

The description gives a specific resource (SEC Form 4 open-market insider purchases by officers, directors, 10% owners) scoped to the RENT ticker, so an agent knows exactly what data comes back. Sibling differentiation is largely carried by the ticker-suffixed tool names rather than the text, which keeps it from a 5.

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 lead word 'Paid' plus the price implies a gating condition (only call if the caller is willing to spend USDC), which is useful implied guidance. However, it never says when to prefer this over buy_insider (the generic sibling), get_schema, or a different ticker variant, and gives no exclusion cases.

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