Skip to main content
Glama
Sign In
hydromancer-mcp

hydromancer-mcp

by joshavenue
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Advanced: any Hydromancer API request

hydromancer_raw_request
Read-only

Send raw Hydromancer /info requests as JSON to query endpoints not covered by other tools, including vault summaries, historical orders, and funding history. Read-only; cannot place orders.

Instructions

Send any Hydromancer /info request directly, for endpoints the other tools do not cover (e.g. vaultSummaries, historicalOrders, spotMeta, outcomeMeta, delegations, perpDexStatus, userFunding, openInterestHistory). Pass the request body as JSON including "type". Full list: https://docs.hydromancer.xyz/llms.txt. Read-only: /info cannot place orders. Binary snapshot endpoints are not supported.

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": {
      "body": "<body>"
    },
    "name": "hydromancer_raw_request"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyYesRequest body, e.g. {"type":"vaultSummaries"} or {"type":"historicalOrders","user":"0x..."}.
limitNoHow many rows to return (default 200, max 5000).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false; the description reinforces with a concrete safety fact ('/info cannot place orders') and adds a real constraint (binary snapshot endpoints unsupported) plus a docs link for the full endpoint list. It does not describe the response shape or error behavior for invalid 'type' values, which is the main remaining gap for a passthrough 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?

Three tight sentences front-loaded with purpose, then supported endpoints, then constraints and the docs pointer. No filler, and the escape-hatch framing comes before the caveats.

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 an open-ended passthrough tool with nested free-form bodies, the description gives the caller everything needed to construct a valid call and defers enumeration to the linked docs. Without an output schema, it could say a bit more about what comes back (raw endpoint payload), which keeps it short of a 5.

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 coverage is 100%, so the schema documents both params, but the description adds the critical semantic constraint that the body must include a "type" key — a requirement not expressed by the schema's permissive additionalProperties object. It doesn't explain how the optional limit interacts with endpoint-specific pagination, but that is a minor omission.

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 ('Send any Hydromancer /info request directly') and immediately frames it as the escape hatch for endpoints the other tools do not cover. The enumerated example endpoints (vaultSummaries, historicalOrders, spotMeta, etc.) make the scope concrete and distinguishable from the fixed-purpose siblings.

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

Usage Guidelines5/5

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

Explicit selection rule: use this when an endpoint isn't covered by the other tools, and the examples show the shape of such cases. It also names when-not: binary snapshot endpoints are unsupported and /info cannot place orders, so an agent knows this tool's boundary.

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