Skip to main content
Glama
Sign In

LFG Alarm

by gm.lfg
OverviewDiscussionsAdmin

Tide times

tide_times
Read-onlyIdempotent

Gives the high and low tides for a place on one day, with each one's height, at the tide station nearest it (named, with its distance), and the next negative low tide and king tide there. Tides are worked out from the station's tidal constants, in the place's own time zone. Predicted tides only: wind and storms move the real water. Read only; sets nothing.

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

Input Schema

NameRequiredDescriptionDefault
dateNoThe day, "2026-11-07". Left out, today at the place.
placeNoA beach, harbour or coastal town, "Santa Cruz". Left out, the person's own tide place is used.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already cover readOnly, idempotent, non-destructive and openWorld, so the bar is lower, yet the description still adds meaningful context: results are computed from the station's tidal constants, expressed in the place's own time zone, and are predictions only since wind and storms move real water. The accuracy caveat and the extra returned artefacts (negative low tide, king tide) are exactly the behavioral detail an agent would otherwise miss.

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 sentences, front-loaded with the output contract, then the computation basis, then the prediction caveat and read-only note. Every clause carries information an agent cannot get from the schema or annotations.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With only two optional string parameters, no output schema and a fully covered schema, the definition supplies the missing return-value picture (heights, station name and distance, follow-on tide events) and the accuracy limitation. Nothing needed to call or interpret it is absent.

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% and both optional parameters already document their defaults (today at the place, the person's own tide place), so baseline 3 applies. The description adds no format or fallback nuance beyond the schema and never mentions the parameters directly.

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?

Specific verb and resource ("Gives the high and low tides for a place on one day") plus the payload contents: heights, nearest named station with distance, next negative low tide and king tide. "Read only; sets nothing" implicitly separates it from set_tide_alarm and sun_times in the sibling list.

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: the read-only framing signals this is the lookup counterpart to set_tide_alarm, but no alternative is named and no when-not condition is stated. It also does not mention pairing sun_times with tides for a combined day view, which would have made routing explicit.

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

All LFG Alarm toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources