Skip to main content
Glama
Sign In
hydromancer-mcp

hydromancer-mcp

by joshavenue
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

List every market and HIP-3 exchange

hydromancer_list_markets
Read-only

List tradable perpetual markets and HIP-3 exchanges, filtered by search text or category such as crypto, stocks, indices, commodities, or FX, to find a market when its exact name is unknown.

Instructions

Lists every tradable perp market, optionally filtered by search text or category (crypto, stocks, indices, commodities, fx), plus the HIP-3 exchanges (perp DEXs) that list stocks and other assets. Use when unsure of a market's exact name.

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

Input Schema

NameRequiredDescriptionDefault
limitNoHow many rows to return (default 100, max 2000).
searchNoText to search for, e.g. "tsla", "gold", "pepe".
categoryNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds useful non-obvious scope: results include HIP-3 exchanges (perp DEXs), not just standard markets. It says nothing about result volume, the 100-row default, or pagination behavior, which matters for a list-everything tool.

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?

Two sentences, both earning their place: scope and return contents first, then the usage cue. No filler or restated title.

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 zero-required-param, read-only listing tool with no output schema, the description covers what is returned, how it can be filtered, and when to reach for it. The one meaningful omission is pagination/limit behavior, which lives only in the schema.

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 67%: limit and search are self-documented, and category's enum is visible in the schema. The description reinforces the category values (crypto, stocks, indices, commodities, fx) and shows the search axis, but adds no syntax or matching-behavior detail beyond the schema. Baseline 3 is appropriate.

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?

Specific verb and resource: lists every tradable perp market plus HIP-3 exchanges, with the optional filters named. It is clearly a discovery/enumeration tool, implicitly distinct from hydromancer_market_snapshot, though it never names a sibling explicitly.

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?

"Use when unsure of a market's exact name" gives a concrete selection condition that routes the agent to this tool for name resolution rather than snapshot/price lookups. No explicit exclusions or named alternatives, but the context is clear enough to choose correctly.

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