Skip to main content
Glama
Sign In
hydromancer-mcp

hydromancer-mcp

by joshavenue
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Price candles (OHLCV)

hydromancer_price_history
Read-only

Fetch candle price history (open, high, low, close, volume) for any market across intervals from 1 second to 1 month, using relative, date, datetime, or Unix ms since/until ranges.

Instructions

Price history as candles (open, high, low, close, volume) for any market. Intervals from 1 second to 1 month. Default: 1h candles for the last 24h. since/until accept Relative ("30m", "6h", "24h", "7d"), a date ("2026-10-01"), a date-time ("2026-10-01T12:00:00Z"), "now", or Unix ms.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "coin": "<coin>"
    },
    "name": "hydromancer_price_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
coinYesMarket name, any case: "BTC", "eth", "HYPE", "kPEPE", or a HIP-3 market such as "xyz:TSLA".
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.
intervalNoCandle size (default "1h"). "1s" only covers about the last 30 minutes.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnly/destructive/openWorld, so the bar is lower, and the description still contributes real behavior: default window, the 1s–1M interval span, and the useful caveat that "1s" only covers about the last 30 minutes. It does not disclose any cap on returned candle count, which matters for wide ranges at fine intervals.

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?

Four dense sentences, front-loaded with what is returned before the parameter format rules. Nothing is repeated unnecessarily and every clause carries information — output shape, interval range, defaults, accepted time formats.

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 names the returned OHLCV fields and the defaults, so an agent can call it blind. The remaining gap is result-size behavior: no mention of how many candles come back or whether large ranges are truncated, which is the main risk for a 1s-interval query.

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 coverage is 100% and the schema already documents coin, since, until, and interval with the same accepted formats the description lists. The description's only added value is combining interval+since+until into a default window statement; it adds no syntax or interaction detail the schema lacks.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb+resource (price history as OHLCV candles for any market) and states the returned fields explicitly. An agent can immediately distinguish this from hydromancer_market_snapshot (current state) or hydromancer_funding_history (a different series).

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?

It gives the defaults (1h candles, last 24h) and the interval range, which frames usage, but never says when to prefer this over hydromancer_market_snapshot or how it pairs with other history tools. No exclusions or explicit alternative routing — usage must be inferred from the resource name.

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