SiteCheck Shop & Social

Spanish weather station observations from AEMET OpenData

social_aemet_spain_weather

Read-only

Spanish weather station observations from AEMET OpenData (official): latest hourly readings (temperature, humidity, wind, pressure, precipitation…) for all stations or one station ID (idema, e.g. 3195 Madrid Retiro), as published by AEMET. Requires the operator's free AEMET OpenData key. Price: $0.002 in USDC per successful call, paid with x402 (Base, Solana or Arc); failed calls are not charged.

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": "social_aemet_spain_weather"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No	Rows, 1 to 500 (default 100)
`station`	No	AEMET station ID (idema), e.g. 3195; empty = all stations

Output Schema

Name	Required	Description	Default
`count`	No
`source`	No
`station`	No
`checkedAt`	No
`observations`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 23, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Annotations already cover readOnlyHint and openWorldHint, and the description adds genuinely new operational context: an AEMET OpenData API key is required, the call costs $0.002 USDC via x402 on Base/Solana/Arc, and failed calls are not charged. Those are the exact facts an agent needs before invoking a paid endpoint, and they are not derivable from the structured fields.

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 the resource and coverage, then the station-scoping rule, then the operational constraints. Every sentence carries information, though the payment-platform enumeration ('Base, Solana or Arc') is slightly heavier than an agent strictly needs.

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?

With an output schema present the description need not explain return values, and the two parameters are fully covered by schema plus description. For a low-complexity, read-only, zero-required-parameter lookup it leaves nothing material unstated: data source, scope, auth requirement, and billing behavior are all given.

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%, so both 'limit' (1-500, default 100) and 'station' are already documented, and the description largely repeats the station semantics with the same style of idema example. It adds no meaning about the limit parameter or the units/format of returned readings, so the baseline of 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 opens with a specific verb+resource: 'Spanish weather station observations from AEMET OpenData (official): latest hourly readings' and enumerates the measurement fields (temperature, humidity, wind, pressure, precipitation). It also distinguishes the two retrieval modes (all stations vs. a single idema), so an agent knows exactly what it gets and at what granularity.

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?

It states the selection rule clearly — pass an idema for one station (with a worked example, 3195 Madrid Retiro) or leave it empty for all stations — which tells the agent how to scope the call. There are no true alternatives among the siblings (nothing else is weather data), but the description never explicitly says when this tool is the right choice versus e.g. a general web search, so it falls short of a 5.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All SiteCheck Shop & Social tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?