Skip to main content
Glama
Sign In
AEMET-MCP

AEMET-MCP

by AnCode666
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get_station_list

Fetch a list of weather stations from Spain's AEMET, optionally filtered by name or province with partial matches.

Instructions

Get a list of all available weather stations or filter by one or more search terms, including approximate matches.

Args: search_terms: Optional terms (space or comma separated) to filter stations by name or province.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_station_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
search_termsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.3/5.0
Behavior3/5

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

No annotations provided, so description carries full burden. It mentions approximate matching but lacks details on pagination, sorting, or read-only nature. Minimal disclosure beyond basic behavior.

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?

Description is short and direct, but includes a redundant 'Args' block that mirrors schema. Could be slightly more concise without losing clarity.

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

Completeness5/5

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

Given tool simplicity (1 optional param, no output schema), description covers purpose and parameter usage fully. No critical gaps for selecting or invoking the tool.

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

Parameters5/5

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

Parameter 'search_terms' is well-described: format (space/comma separated) and filtering scope (name or province). Adds significant value beyond schema (0% coverage).

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?

Description clearly states it retrieves a list of weather stations, optionally filtered by search terms with approximate matching. It distinguishes from siblings like find_nearby_stations which is location-based.

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?

Implies use for listing stations vs. other tools like find_nearby_stations or get_station_data, but does not explicitly state when not to use or provide alternatives.

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