Skip to main content
Glama

Ipma Locations

ipma_locations
Read-onlyIdempotent

List the Portuguese cities and islands IPMA publishes weather forecasts for, district capitals plus Madeira and Azores islands, with their globalIdLocal codes and coordinates region. Filter by name. Example: ipma_locations({ query: "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": {
      "query": "faro"
    },
    "name": "ipma_locations"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryNoOptional name filter (accent-insensitive substring), e.g. "faro", "santa".

Schema Changelog

Changes observed during successful MCP inspections.

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

TDQS

A3.9/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, so safety is covered. The description adds substantive behavioral content beyond them: the enumeration scope (district capitals plus the two island groups) and that returned records carry globalIdLocal codes and coordinates, which tells the agent what it will get back.

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 plus a concrete example, with no filler. The phrase 'coordinates region' is slightly garbled, which keeps it from a 5, but overall it is tight and well-ordered.

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 simple read-only lookup with no output schema, the description covers what the tool enumerates and what fields accompany each entry. Minor gaps remain around ordering and result volume, but nothing essential for correct invocation is missing given the annotations already state the safety profile.

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 single query parameter is fully documented there, including accent-insensitive substring matching. The description restates the name filter and supplies a concrete example call, adding only marginal meaning beyond the schema, so the baseline 3 applies.

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 names a specific verb (List) and resource (Portuguese cities/islands IPMA forecasts for), and scopes the contents precisely: district capitals plus Madeira and Azores, with globalIdLocal codes and coordinate region. This clearly distinguishes it from the forecast siblings, which consume these codes rather than enumerate them.

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: the emphasis on globalIdLocal codes signals this is a lookup/seed tool for the forecast tools, and the filter example shows one call pattern. There is no explicit statement of when to use this instead of ipma_forecast, or when-not to call it.

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.