Skip to main content
Glama
Sign In
hydromancer-mcp

hydromancer-mcp

by joshavenue
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

My Hydromancer API usage

hydromancer_my_usage
Read-only

Retrieve your Hydromancer API usage by day and request type, including requests, failures, response times, and tokens consumed, to monitor performance and diagnose issues.

Instructions

Your own Hydromancer API usage by day and request type: requests, failures, response times and tokens consumed.

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

Input Schema

NameRequiredDescriptionDefault
daysNoDays to look back (default 7).

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 that data is bucketed by day and request type and lists the returned metrics, which is useful, but says nothing about scope of history, aggregation limits, or cost/latency of the call.

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?

One front-loaded sentence that states scope and returned metrics with zero filler. Everything present earns its place.

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?

A simple read-only, one-optional-param tool whose annotations cover safety and whose schema covers the only parameter; the description fills the remaining gap by enumerating the metrics returned even though no output schema exists. Only minor detail (e.g., default aggregation granularity) is missing.

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 single `days` parameter already documents its default and 1-90 range, so the schema carries the burden. The description never references the lookback window at all, so it adds no parametric meaning beyond the schema.

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?

Names the specific resource (the caller's own Hydromancer API usage) and the exact breakdown dimensions (by day and request type) plus the metrics returned. No sibling covers usage reporting, so an agent can distinguish it immediately.

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 only implied by 'Your own ... usage' — there is no explicit statement of when to call it versus siblings, no mention of prerequisites (e.g., that it reports on the current API key), and no exclusions. Adequate but leaves routing to inference.

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