Skip to main content
Glama
jocarrd

aemet-mcp

by jocarrd
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Maritime forecast for Spanish coastal waters and high seas

get_maritime_forecast

Get an AEMET maritime bulletin for any Spanish sea area: wind, sea state, visibility, warnings, and validity period. Works for coastal waters and high seas using common names or codes.

Instructions

Returns the AEMET maritime bulletin for a sea area: sea state, wind, visibility, warnings and the validity period. Two products are covered: coastal waters (8 bulletins, one per stretch of the Spanish coast, each split into per-province zones and carrying the marine warnings) and high seas (3 bulletins covering the Atlantic north of 30N, the Atlantic south of 35N and the Mediterranean). Areas can be named the way people and the media name them, or given as AEMET codes.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
areaYesSea area to forecast. Accepts the name people use ('Cantábrico', 'Golfo de Cádiz', 'Baleares', 'Canarias', 'Mediterráneo', 'Atlántico'), a coastal community or province ('Asturias', 'Málaga', 'Girona'), an AEMET high seas zone ('Gran Sol', 'Finisterre', 'Alborán'), or an AEMET area code: 0-2 for high seas, 40-47 for coastal waters.
productNoWhich AEMET product to read. 'coastal' covers Spanish coastal waters out to a few miles and carries warnings; 'high_seas' covers the open Atlantic and Mediterranean zones. Omit to pick the one that matches the area.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It discloses the scope (coastal vs high seas), content (sea state, wind, etc.), and that coastal carries warnings, which is useful. However, it doesn't mention any potential limitations, such as data availability, update frequency, or whether the bulletin is text-only vs structured. For a read-only forecast tool, this is moderately transparent but not exhaustive.

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 a single paragraph with dense, useful information. It front-loads the core purpose and then details the two products and naming options, all without redundancy. Every sentence adds value.

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 tool's moderate complexity (2 params, no output schema), the description covers the key aspects: what data is returned, product types, and area naming. It doesn't explicitly describe the output format, but since there's no output schema, a brief note on return structure would improve completeness. Minor gap.

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%, so the schema already describes both parameters thoroughly. The description adds context about naming flexibility and product selection, reinforcing the schema but not adding new syntactic details. 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 clearly states it returns an AEMET maritime bulletin (sea state, wind, visibility, warnings, validity period) for a sea area. It distinguishes two product types (coastal and high seas) and mentions how areas can be named. It doesn't explicitly contrast with siblings like get_beach_forecast, but the maritime specificity makes it distinct.

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 implies when to use it: when a maritime bulletin is needed, and it explains the two product types and naming flexibility. It doesn't explicitly say when not to use it or name alternatives (e.g., beach forecast for coastal beaches), but the guidance is clear enough for an agent to select it over non-maritime tools.

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

Deploy Server

Other Tools