Skip to main content
Glama

Ipma Uv Forecast

ipma_uv_forecast
Read-onlyIdempotent

UV index forecast for Portugal from IPMA, daily peak-hours ultraviolet index for a Portuguese city (Lisbon, Porto, Algarve, Madeira, Azores) for the next ~3 days, with risk level (Low to Extreme). Example: ipma_uv_forecast({ city: "Faro" })

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": "Faro"
    },
    "name": "ipma_uv_forecast"
  }
}

Input Schema

NameRequiredDescriptionDefault
cityYesPortuguese city, e.g. "Lisboa", "Porto", "Faro", "Funchal". Accent-insensitive.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
      +  {
      +    "city": "Faro"
      +  }
      +]
  2. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds genuinely behavioral detail: the forecast horizon (~3 days) and what the payload contains (peak-hours index plus a risk band). It says nothing about update cadence or whether island names resolve to multiple stations, which given openWorldHint=true would be useful.

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?

One front-loaded sentence carrying region, granularity, horizon and output, followed by a compact example. The parenthetical mixes cities (Lisbon, Porto) with regions/islands (Algarve, Madeira, Azores), which is slightly imprecise but not wasteful.

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 single-parameter, no-output-schema read tool with full annotation coverage, the description is essentially complete: it says what is returned, over what horizon, from which source. The only omission is how to disambiguate region-style values against city-style values.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and the schema already documents `city` with examples and accent-insensitivity, so the baseline is 3. The description adds value by expanding the accepted value space with region/island names (Algarve, Madeira, Azores) and a worked example call, which is more than the schema alone conveys.

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?

States a specific verb and resource ('UV index forecast for Portugal from IPMA'), plus scope (daily peak-hours, next ~3 days) and output content (risk level Low to Extreme). The UV-index framing naturally separates it from the plain weather and sea-forecast siblings, though it never names or contrasts them directly.

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 by scope: call it when you need UV data for a Portuguese city. There is no explicit when-to-use/when-not statement or guidance on choosing between this and the general ipma_forecast, which plausibly also carries UV information.

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.