Skip to main content
Glama

SouthPow crypto & market data

buy_insider_QTEX

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

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

Input Schema

NameRequiredDescriptionDefault
limitNoRows, 1-100 (default 20)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior4/5

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

With no annotations, the description carries the full behavioral burden and does well: it discloses paid access ($0.05 USDC on Base), no account or API key required, the exact SEC Form 4 scope, and that data is 'as filed.' It omits response format, error/refund behavior, and rate limits, but provides substantial context beyond a bare endpoint label.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely short and front-loaded with 'Paid' and the data scope. Every fragment earns its place: source, eligibility, price, auth, and endpoint URL.

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 one-parameter paid data-fetch tool with no annotations and no output schema, the description supplies source, scope, cost, authentication expectations, and endpoint URL. It does not describe return fields or failure handling, but the essentials for correct invocation are present.

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?

The input schema fully documents the single optional 'limit' parameter (rows 1-100, default 20), and the description adds no parameter meaning. With 100% schema description coverage, the baseline score of 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?

The description clearly identifies the resource: QTEX insider BUYS from SEC Form 4, limited to open-market purchases by officers, directors, and 10% owners. The ticker token and URL make it ticker-specific among sibling buy_insider_<TICKER> tools, though no explicit verb or sibling differentiation is stated.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no explicit when-to-use guidance or comparison with alternatives such as the base buy_insider tool or other ticker-specific variants. The word 'Paid' signals a cost condition, but the agent must infer selection from the name and URL.

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