Skip to main content
Glama
Sign In
hydromancer-mcp

hydromancer-mcp

by joshavenue
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Recent liquidations

hydromancer_recent_liquidations
Read-only

Retrieve force-closed positions for one market or the whole exchange, newest first, with totals by side. Use it to inspect liquidation activity over a chosen window, defaulting to the last 24 hours.

Instructions

Positions that were force-closed (liquidated), newest first, for one market or the whole exchange, with totals by side. "Long liquidated" means a long position was wiped out. Default window: last 24h.

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": "hydromancer_recent_liquidations"
  }
}

Input Schema

NameRequiredDescriptionDefault
coinNoMarket to check; omit for every market.
limitNoHow many rows to return (default 50, max 1000).
sinceNoStart of window. Relative ("30m", "6h", "24h", "7d"), a date ("2026-10-01"), a date-time ("2026-10-01T12:00:00Z"), "now", or Unix ms. Default "24h".
untilNoEnd of window. Default now.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, non-destructive, open-world), so the description's added value is the default time window, sort order, and the by-side aggregation. It also pre-empts a likely misreading by defining 'long liquidated'. It does not mention pagination or result volume behavior beyond the schema's limit.

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?

Three short sentences, front-loaded with what the tool returns, followed by the one disambiguation likely to matter and the default window. No filler.

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?

With no output schema, the description usefully conveys ordering and the presence of per-side totals, and the default window. For a simple read tool with full schema coverage and clear annotations, this is close to sufficient; only result-size/pagination expectations are unstated.

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%, so coin, limit, since, and until are already fully documented. The description only restates the market-vs-all-exchange scope and the 24h default, adding no syntax, precedence, or edge-case detail beyond the schema.

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 (force-closed/liquidated positions) with ordering (newest first), scope (one market or whole exchange), and output shape (totals by side). It is clearly distinct from wallet- and market-oriented siblings, though it never names an alternative explicitly.

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?

Implies usage via 'for one market or the whole exchange' and a stated default window of 24h, which helps an agent decide scope. There is no explicit when-to-use vs when-not guidance or named alternative among the many hydromancer siblings.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools