Skip to main content
Glama
Sign In
AEMET-MCP

AEMET-MCP

by AnCode666
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get_daily_forecast

Retrieve the daily weather forecast for any Spanish municipality by providing its AEMET municipality code.

Instructions

Get the daily weather forecast for a Spanish municipality.

Args: municipality_code: AEMET municipality code (e.g., "28079" for Madrid)

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": {
      "municipality_code": "<municipality_code>"
    },
    "name": "get_daily_forecast"
  }
}

Input Schema

NameRequiredDescriptionDefault
municipality_codeYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.1/5.0
Behavior2/5

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

With no annotations, the description carries full burden but only states it returns a 'daily weather forecast.' It omits critical behavioral details such as units, time range, data source, safety (read-only), and potential limitations (e.g., only for today or extended forecast).

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 description is extremely concise (two sentences) with no wasted words. It front-loads the purpose and includes parameter explanation. Minor improvement would be to mention the output format briefly.

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

Completeness2/5

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

For a simple one-parameter tool, the description is incomplete. It does not specify output format, units, or whether multiple days are returned. Since there is no output schema, more content is needed to ensure proper tool usage.

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 0%, so the description must compensate. It explains 'municipality_code' as an AEMET code with an example ('28079' for Madrid). This adds value beyond the schema's type/title, but lacks guidance on how to obtain the code (e.g., via search_municipality_code).

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 clearly states 'Get the daily weather forecast for a Spanish municipality,' specifying the verb (get), resource (daily weather forecast), and scope (Spanish municipality). This purpose is distinct from sibling tools like get_station_data or get_beach_data_uv.

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

Usage Guidelines2/5

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

No guidance on when to use this tool versus others (e.g., search_municipality_code or get_historical_data). The description does not mention prerequisites or alternative approaches, leaving the agent with no decision context.

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