Skip to main content
Glama
Sign In
hydromancer-mcp

hydromancer-mcp

by joshavenue
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Funding rate history for a market

hydromancer_funding_history
Read-only

Fetch hourly funding rates for a market over a chosen window, including average and annualized rates, to assess whether longs pay shorts.

Instructions

Hourly funding rates for a market over time, with the average and annualized rate. Positive funding means longs pay shorts. Default window: last 7 days.

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_funding_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 "7d".
untilNoEnd of window. Default now.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds genuinely useful context beyond them: hourly granularity, that results include average and annualized rates, and the domain rule that positive funding means longs pay shorts. It omits limits such as maximum lookback or result caps, which keeps it from a 5.

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?

Three short sentences with the resource and return shape front-loaded; nothing is buried. The closing default-window sentence mildly duplicates the schema's since default, a small redundancy rather than a flaw.

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?

For a simple read-only lookup with full schema coverage, annotations and no output schema, the description covers what the tool returns (hourly rates, average, annualized) and the default time window. Only edge-case behavior such as maximum range or empty results is unaddressed.

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 the schema already documents coin, since (with relative/date/unix formats) and until. The description only restates the 7-day default window, adding nothing about accepted input formats or timezone handling beyond what the schema provides. Baseline 3 applies.

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?

States a specific verb and resource: hourly funding rates for a market over time, plus the aggregate values returned (average and annualized rate). No sibling exposes funding rates, so the agent can distinguish it from hydromancer_price_history or hydromancer_market_snapshot without opening the schema.

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 implied by the purpose rather than stated: the description notes the default window (last 7 days) but never says when to pick this tool over price history or a market snapshot, nor any exclusions or prerequisites. Adequate for a self-evident lookup tool, but no explicit 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