Skip to main content
Glama
Sign In
hydromancer-mcp

hydromancer-mcp

by joshavenue
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Market snapshot: price, 24h volume, open interest

hydromancer_market_snapshot
Read-only

Fetch mark, oracle, and mid prices plus 24h volume and open interest in coins and USD for selected markets, or omit coins to see top markets by volume.

Instructions

Current mark/oracle/mid price, 24h volume and open interest (in coins and USD) for one or more markets. Leave coins empty for the top native markets by 24h volume, which also shows max leverage. Works for HIP-3 markets (e.g. "xyz:TSLA").

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

Input Schema

NameRequiredDescriptionDefault
topNoWhen coins is empty, how many top markets by 24h volume (default 15).
coinsNoMarkets to show, e.g. ["BTC","ETH","xyz:TSLA"]. Omit for the busiest markets.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already establish readOnlyHint=true, openWorldHint=true, and destructiveHint=false, so safety behavior is covered. The description adds useful behavioral context: the empty-coins path returns top native markets by 24h volume and also shows max leverage, and HIP-3 markets are supported. It does not discuss rate limits, authentication, or pagination.

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 compact sentences front-load what is returned, then explain the empty-coins case and HIP-3 support. There is no filler or repetition.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple read-only snapshot tool with two optional parameters, full schema coverage, and clear annotations, the description covers the returned fields, default top-market behavior, and special market identifiers adequately. No output schema is present, and the description already names the key returned metrics.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the baseline is 3. The description adds meaning by explaining the special empty-coins behavior and that the top-market path includes max leverage, plus a HIP-3 example, which goes beyond the schema text.

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 states the resource and returned metrics: current mark/oracle/mid price, 24h volume, and open interest for one or more markets. It distinguishes itself implicitly from historical tools like price_history by emphasizing current snapshot data, but it does not explicitly name sibling alternatives such as list_markets or price_history.

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

Usage Guidelines4/5

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

It gives clear usage context: pass specific coins for one or more markets, leave coins empty for top native markets by 24h volume, and use HIP-3 identifiers like "xyz:TSLA". It lacks explicit when-not-to-use guidance or named alternatives, so it stops short of full routing guidance.

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