Skip to main content
Glama

get_water

Read-onlyIdempotent

One public water by id or slug: stocking history, species, and depth or water level when we have them, plus its castthewater.com page URL. A closed state is not available.

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": "get_water"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugNoPublic slug or waters path, such as ny/essex/lake-placid
water_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world, so the safety profile needs no restating. The description adds genuine context the annotations don't: the payload includes stocking history, species, depth/water level, and a castthewater.com page URL, and critically that some attributes may be absent ('when we have them') and that closed states are not returned at all.

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?

A single dense sentence with the resource and its return contents front-loaded, followed by a short scope caveat. Nothing is decorative, though the 'when we have them' qualifier is slightly awkward and its placement obscures which fields are optional.

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 carries the burden of describing returns and does so by listing the field groups plus the external page URL. Remaining gaps -- how id and slug interact, and what happens on a miss -- are minor for a simple read-only lookup.

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 50%: slug is documented (including the 'ny/essex/lake-placid' path format) but water_id has no description. The description confirms 'id or slug' as the lookup keys, but says nothing about precedence when both are supplied or about behavior when neither of these optional parameters is given. 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?

States a specific verb and resource -- fetch one public water by id or slug -- and enumerates what comes back (stocking history, species, depth/water level, page URL). Compared with the plural siblings search_waters and get_recent_stockings, the singular 'One public water' scope makes the distinction clear without naming them.

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: use this for a single known water rather than a search or a recent-stockings list. No explicit when-to-use/when-not guidance or named alternative is given, and 'A closed state is not available' describes a data gap rather than a selection rule.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources