Skip to main content
Glama

search_waters

Read-onlyIdempotent

Search public waters by name. Optional two-letter state. Only states open for indexing are returned, each with its castthewater.com page URL. At most 25 hits.

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": {
      "query": "<query>"
    },
    "name": "search_waters"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesWater name or fragment
stateNoOptional US state abbreviation. Closed states are not available.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover the read-only, idempotent, non-destructive profile, yet the description adds genuinely non-obvious behavior: results are silently limited to states open for indexing and capped at 25 hits. It also discloses that each hit carries a castthewater.com page URL. It stops short of explaining what happens when more than 25 waters match.

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?

Four short sentences, front-loaded with the purpose and followed by the scope caveat, return content, and result cap. No filler and nothing redundant.

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 two-parameter read search with full annotations and no output schema, the description covers scope, filtering caveat, returned field, and result limit. The only meaningful gap is whether the 25-hit cap implies truncation that cannot be paged.

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 both parameters are already documented, including that query accepts a name or fragment. The description only restates the optional two-letter state and reinforces the closed-state restriction, adding little syntax or format detail beyond the schema.

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 ('Search public waters by name') plus the matching scope, so an agent can tell it is a name-lookup rather than a generic search or a get-by-id call. It does not explicitly contrast itself with siblings like search or get_water, keeping it just short of a 5.

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?

The optional state parameter and the note that only indexed states are returned imply when this tool is useful, but there is no explicit statement of when to prefer it over search or get_water, nor any exclusion guidance. Usage is inferable rather than stated.

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