Skip to main content
Glama

Lake conditions

conditions
Read-onlyIdempotent

Current USGS lake-level and water readings for Finger Lakes gauges that are reporting (provisional), with official links for lakes that are not.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

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 declare readOnly, idempotent, non-destructive, and closed-world, so safety is covered. The description adds two genuinely useful behavioral facts beyond them: values are provisional, and lakes that are not reporting return official links instead of readings. It does not state refresh cadence or staleness windows, which would complete the picture.

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 front-loaded sentence with no filler, leading with the resource and currency. The trailing clause 'for lakes that are not' is slightly elliptical (not reporting) and costs a moment of parsing, which keeps it from a 5.

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 explaining what comes back, and it does so at a high level: current readings for reporting gauges plus official links for those that are not. It stops short of describing the shape of a reading (units, gauge identifiers, timestamps), which is the remaining gap.

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?

The tool takes no parameters, so there is nothing for the description to disambiguate; the baseline for a zero-parameter tool applies. The description correctly implies the scope is fixed to Finger Lakes gauges rather than requiring a lake argument.

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?

The description names a concrete resource (USGS lake-level and water readings for Finger Lakes gauges) and qualifies currency (current, provisional), so an agent can tell this apart from siblings like events, news, or get_indicators. It does not explicitly contrast itself with a sibling, which keeps it 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?

Usage is implied rather than stated: 'current' readings suggest a present-conditions lookup, and the mention of official links hints that non-reporting lakes are still covered. There is no explicit when-to-use, when-not-to-use, or named alternative, so an agent must infer routing.

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