Skip to main content
Glama

Weatherapi

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Marine

marine
Read-onlyIdempotent

Get marine/ocean conditions forecast for a coastal location: significant wave height, swell height, water temperature, and wind. Up to 7 days, sampled every 6 hours. Example: marine({ q: "33.7,-118.4", days: 2 }).

Input Schema

NameRequiredDescriptionDefault
qYesLocation — city name (e.g. "London"), "lat,lon" (e.g. "48.8567,2.3508"), US/UK/Canada zip/postcode, IATA airport code (e.g. "DXB"), or "auto:ip". NOTE on IATA codes: WeatherAPI resolves them to that airport's CITY, not the airport's own weather station — for the actual airport-station reading (can differ by several degrees) use the aviation-weather pack's metar tool with the airport's ICAO code instead.
daysNoNumber of marine forecast days (default 1, max 7).
_apiKeyNoOptional — your own WeatherAPI.com API key for higher limits; omit to use the shared Pipeworx key.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / q / description
      Previous value: -"Location — city name (e.g. \"London\"), \"lat,lon\" (e.g. \"48.8567,2.3508\"), US/UK/Canada zip/postcode, IATA airport code (e.g. \"DXB\"), or \"auto:ip\"."New value: +"Location — city name (e.g. \"London\"), \"lat,lon\" (e.g. \"48.8567,2.3508\"), US/UK/Canada zip/postcode, IATA airport code (e.g. \"DXB\"), or \"auto:ip\". NOTE on IATA codes: WeatherAPI resolves them to that airport's CITY, not the airport's own weather station — for the actual airport-station reading (can differ by several degrees) use the aviation-weather pack's metar tool with the airport's ICAO code instead."
  2. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "days": 2,
+    "q": "33.7,-118.4"
+  }
+]
  3. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations mark the tool read-only, idempotent, and non-destructive; the description adds behavioral details such as a 7-day forecast horizon, 6-hour sampling interval, and the specific data fields returned, which usefully extends the annotation-only picture.

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?

The description is two sentences plus a compact example, front-loading the purpose and providing a concrete usage illustration with zero filler.

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?

Given the absence of an output schema, the description compensates by listing the marine data fields (wave height, swell, water temp, wind), the forecast window, and a code example, making it reasonably complete for a read-only forecast tool.

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 for parameters is 100% with detailed descriptions, and the description only reinforces the example call and the 7-day limit without introducing new parameter semantics, so a baseline 3 is appropriate.

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?

The description opens with a specific verb phrase 'Get marine/ocean conditions forecast for a coastal location' and enumerates the key fields (wave height, swell, water temperature, wind), clearly differentiating it from the general weather 'forecast' sibling by focusing on marine conditions.

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?

The description sets the context as a marine/ocean forecast for coastal locations, which implies when to use it, but it does not explicitly state exclusions or name alternative tools for non-marine queries, so it falls short of full usage guidance.

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

All Weatherapi 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