SiteCheck Agent Intel & Dev

Current wave height and period at a coordinate, and, when

agent_intel_marine_weather_tide_forecast

Read-only

Current wave height and period at a coordinate (Open-Meteo Marine), and, when a US NOAA tide station id is given, the next high and low tide predictions for the next 24 hours. Tide predictions exist only for NOAA stations; no wind or pressure forecast is included. Price: $0.002 in USDC per successful call, paid with x402 (Base, Solana or Arc); failed calls are not charged.

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": {
      "latitude": "<latitude>",
      "longitude": "<longitude>"
    },
    "name": "agent_intel_marine_weather_tide_forecast"
  }
}

Input Schema

Name	Required	Description
`station`	No	Optional NOAA tide station id (7 digits), e.g. 9413450 (Monterey)
`latitude`	Yes	Latitude, -90 to 90
`longitude`	Yes	Longitude, -180 to 180

Output Schema

Name	Required	Description	Default
`note`	No
`waves`	No
`source`	No
`station`	No
`latitude`	No
`tides24h`	No
`checkedAt`	No
`longitude`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 23, 2026

TDQS

A3.9/5.0

Behavior3/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered by structured data. The description adds genuinely useful non-schema context — cost of $0.002 USDC per successful call via x402 across Base/Solana/Arc and that failed calls are not charged — which matters for an agent budgeting calls. It does not say whether the wave figures are instantaneous observations or a modelled forecast, which is the main behavioral ambiguity left.

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?

Front-loaded with the primary output and split into a separate billing sentence, with no filler. The opening sentence is an awkward run-on ('at a coordinate ..., and, when ... is given, the next high and low tide predictions'), which slightly hurts scannability.

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?

An output schema exists, so return values need no explanation, and the description covers required inputs, the optional parameter's effect, source limits, and payment terms. The one remaining gap is whether 'Current' means live observation or nearest model timestep, plus the 24-hour tide horizon being stated only for tides and not waves.

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 the schema already documents latitude/longitude ranges and the 7-digit NOAA station example, so baseline is 3. The description only restates that station is the NOAA tide station id; it adds no format or semantics 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?

States a specific verb and resources: 'Current wave height and period at a coordinate (Open-Meteo Marine)' plus 'next high and low tide predictions'. Both the data source and the conditional tide behavior are named, so an agent knows exactly what it gets without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Clearly frames when the optional station parameter applies ('when a US NOAA tide station id is given') and states the boundary condition 'Tide predictions exist only for NOAA stations'. It also rules out scope creep with 'no wind or pressure forecast is included', though it names no alternative tool for those needs.

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

All SiteCheck Agent Intel & Dev tools Inspect

Try in Browser

Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?