Skip to main content
Glama

SouthPow crypto & market data

buy_insider_UXIN

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

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

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, the description carries the full behavioral burden and does a reasonable job: it discloses that the call is paid ($0.01 USDC on Base), that no account or API key is needed, and that data provenance is SEC Form 4 as filed. It omits what happens on payment failure, whether results are cached/refreshed, and what the response body looks like.

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?

Roughly two sentences, front-loaded with the 'Paid' flag so a caller sees the cost implication immediately, followed by content, price/network, access requirements, and endpoint. No filler or repetition.

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-like data endpoint the description covers cost, auth, and source well, but with no output schema and no annotations it leaves the caller guessing about return shape (row fields, ordering, empty-result behavior). That is the main remaining gap for a tool of this simplicity.

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 already documents its 1-100 range and default of 20. The description adds no meaning beyond the schema, 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?

States a specific verb, resource, and data source: insider BUYS for UXIN drawn from SEC Form 4 open-market purchases by officers, directors, and 10% owners. That cleanly separates it from the generic buy_insider sibling and from buy_coin_*/buy_pm_* families, though it never explicitly names the generic sibling as the broader alternative.

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?

Usage is only implied by the ticker-scoped name and the Form 4 sourcing; there is no explicit statement of when to pick this over buy_insider (all tickers) or how to handle a ticker with no Form 4 activity. The access notes (paid, no account) help a caller decide it is viable but are not selection guidance.

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