Skip to main content
Glama

SouthPow crypto & market data

buy_insider_SYNX

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

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

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 meaningful traits: paid access, the exact price and chain, no account or API key needed, and the upstream source (SEC Form 4 as filed). It omits how payment is actually executed (no payment parameter exists in the schema), what happens on payment failure, and any rate limits, which are significant gaps for a monetized 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?

Very short and front-loaded: 'Paid' appears first, followed by data scope, cost, auth, and endpoint. Every fragment carries information; the raw URL inline is slightly clunky but functional, and the telegraphic phrasing borders on under-specified rather than verbose.

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 tool with no output schema and no annotations, the description covers source, price, and auth, which is a lot of what an agent needs. It still does not describe the response shape (e.g., transaction rows, fields returned) or the payment handshake, both of which an agent must understand before invoking a paid endpoint.

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 description coverage is 100% and the single 'limit' parameter is documented in the schema as rows 1-100 with a default of 20. The description adds nothing beyond that, so the baseline 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 names a specific verb and resource ('SYNX insider BUYS from SEC Form 4') and narrows scope to open-market purchases by officers, directors, and 10% owners, so an agent knows exactly what data it yields. It does not explicitly distinguish itself from the generic 'buy_insider' sibling or from 'buy_coin_SYNX', leaving ticker-variant routing to the tool name alone.

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?

'Paid ... $0.25 USDC on Base. No account, no API key.' implies a cost/prerequisite, which is useful context for deciding to call. However, there is no explicit when-to-use guidance, no statement about when to prefer the generic buy_insider over this ticker-specific variant, and no exclusion conditions.

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