Skip to main content
Glama

Ipma Forecast

ipma_forecast
Read-onlyIdempotent

Portugal weather forecast, official IPMA 5-day forecast for a Portuguese city: Lisbon, Porto, Faro, the Algarve, Madeira (Funchal), Azores (Ponta Delgada). Returns daily min/max temperature (°C), precipitation probability, weather description in English, and wind direction/strength. Example: ipma_forecast({ city: "Lisboa" })

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": {
      "city": "Lisboa"
    },
    "name": "ipma_forecast"
  }
}

Input Schema

NameRequiredDescriptionDefault
cityYesPortuguese city or island, e.g. "Lisboa", "Lisbon", "Porto", "Faro", "Funchal", "Ponta Delgada". Accent-insensitive; use ipma_locations to browse all 35.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
      +  {
      +    "city": "Lisboa"
      +  },
      +  {
      +    "city": "Porto"
      +  }
      +]
  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, openWorld and non-destructive, so safety is covered. The description adds value beyond that by disclosing the forecast horizon (5 days), the exact returned fields (min/max °C, precipitation probability, English weather description, wind direction/strength), and that the source is official IPMA data.

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?

Three sentences, front-loaded with purpose and geography before return values and a usage example. The city list partially duplicates the schema's example values, but nothing is wasted or buried.

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?

With no output schema, the description correctly compensates by enumerating return fields and units, and the single required parameter is fully documented in the schema. Only the lack of sibling routing (sea/UV forecasts, ipma_locations) keeps it from being fully complete for an agent choosing among many weather-adjacent tools.

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% and the parameter description already documents accent-insensitivity, example values, and the ipma_locations cross-reference. The description adds only geographic reach (islands and the Algarve) and a worked call example, so it sits at the baseline rather than adding new syntactic or semantic constraints.

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 verb and resource ('official IPMA 5-day forecast for a Portuguese city') and enumerates the covered geography (Lisbon, Porto, Faro, Algarve, Madeira/Funchal, Azores/Ponta Delgada), which makes the scope concrete. It does not explicitly distinguish itself from siblings like ipma_sea_forecast or ipma_uv_forecast, though 'daily min/max temperature, precipitation, wind' implicitly scopes it to general weather.

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: an agent can infer this is the tool for Portuguese city weather, but there is no explicit when-to-use statement, no exclusions, and no pointer to ipma_locations or the sea/UV forecast siblings. Routing guidance lives only in the schema's city parameter description, not in the description itself.

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.