Skip to main content
Glama

Ipma Sea Forecast

ipma_sea_forecast
Read-onlyIdempotent

Sea state forecast for the Portuguese coast from IPMA oceanography, significant wave height (m), wave period (s), wave direction, and sea surface temperature (°C) for 12 coastal zones on the mainland, Madeira, and Azores. Good for surf, sailing, and beach conditions. Example: ipma_sea_forecast({ city: "Sagres" })

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "day": 0,
      "city": "Sagres"
    },
    "name": "ipma_sea_forecast"
  }
}

Input Schema

NameRequiredDescriptionDefault
dayNoForecast day: 0 = today (default), 1 = tomorrow, 2 = day after.
cityNoOptional coastal zone filter, e.g. "Sagres", "Lisboa", "Porto", "Funchal", "Ponta Delgada". Omit for all 12 zones.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
      +  {
      +    "city": "Sagres",
      +    "day": 0
      +  },
      +  {
      +    "city": "Funchal"
      +  }
      +]
  2. First observed

TDQS

A3.7/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 open-world behavior, so the safety profile is fully covered. The description adds genuine value beyond those hints by enumerating the returned fields with units, which matters because no output schema exists. It does not mention update frequency or data freshness, but that gap is modest.

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?

The content is front-loaded: what the tool returns, then coverage, then use cases, then a call example. Every sentence contributes, though the 'Good for surf, sailing, and beach conditions' clause is the least load-bearing. No redundancy or filler elsewhere.

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 two-parameter read-only forecast tool with no output schema, the description supplies the missing return-value detail (variables and units) and geographic scope. Optionality and defaults are handled by the schema. Only the refresh cadence of the forecast is unstated.

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 is 100%, with both 'day' and 'city' fully documented in the schema including defaults and example values. The description reinforces the city filter through the Sagres example and the 12-zone scope, but adds no new syntax or constraint information beyond the schema. Baseline 3 is appropriate.

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 specific resource (sea state forecast for the Portuguese coast) and enumerates the exact variables returned: wave height in meters, period in seconds, direction, and SST in Celsius. It scopes coverage to 12 zones across the mainland, Madeira, and Azores. It does not explicitly differentiate itself from sibling ipma_forecast or ipma_uv_forecast, which keeps it at 4 rather than 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 only implied through the phrase 'Good for surf, sailing, and beach conditions,' which suggests consumer contexts but gives no when-not guidance and names no alternative tool for land weather or UV data. An agent must infer that this is the marine-specific sibling of the general forecast.

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.