A weather and environmental telemetry server that aggregates readings from multiple IoT collectors (Airthings, Shelly, SwitchBot, Netatmo) and provides weather forecasts, air quality data, and contextual information via REST and MCP APIs
Polar has 26 tools with consistent naming (verb_noun pattern) and basic descriptions. However, most descriptions are generic (50-80 chars, below the 194-char baseline) and lack actionable context. Input schemas are present but minimal, most parameters lack type constraints, enums, or validation guidance. No output schemas documented. Error handling is absent from tool definitions. The server exposes write operations (submit_command, update_command_status) without confirmation patterns or permission gates. Alias tools (get_forecast/get_weather_forecast) signal composition issues.
Retrieves current air quality data for a target location
Retrieves air quality forecast for a target location
Retrieves astronomical context data (sunrise, sunset, moon phase) for a target location
Retrieves audit events within a time range, optionally filtered by event type
Retrieves a comprehensive climate snapshot for a target location
Retrieves the status and result of a submitted command
Duplicate/alias tools reduce clarity. get_forecast and get_weather_forecast are identical; get_weather_forecast and get_weather_current are near-duplicates. LLMs waste reasoning cycles deciding between them.
No output schemas documented. LLMs cannot plan downstream calls or extract required fields (e.g., does get_latest_readings return metric names, timestamps, units?). Baseline: 100% of A+ tools document return types.
Descriptions are generic and under 100 chars (baseline 194 chars). Examples: 'Returns the health status of the weather station' (55 chars), 'Retrieves UV index data for a target location' (50 chars). Lack actionable context: when to call instead of similar tools, what data is returned, prerequisites.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | C | 64 | 2026-07-28+ | v2 |
Retrieves a report of data gaps in the telemetry collection
Retrieves the weather forecast for a target location
Retrieves the latest sensor readings from all collectors
Retrieves a snapshot of server metrics
Retrieves neighborhood air quality data from PurpleAir sensors
Retrieves pollen data and forecasts for a target location
Returns the health status of the weather station
Retrieves UV index data for a target location
Retrieves active weather alerts for a target location
Retrieves current weather conditions for a target location
Alias for get_forecast - retrieves the weather forecast for a target location
Retrieves wildfire data and context for a target location
Returns the capabilities of the Polar server including available metrics and features
Lists recent commands for a target location
Retrieves consent grants for configured integrations
Retrieves license information for all data providers
Returns the list of configured target locations/stations
Queries historical sensor readings for a specific metric within a time range
Submits a command to a device capability
Updates the status of a submitted command with observed effects or errors
Write operations (submit_command, update_command_status) lack confirmation/dry-run patterns and no permission gates visible. Agents can invoke destructive commands without safeguards. No error guidance for recovery.
Parameter 'target' is optional with implicit default behavior ('uses default if not specified'). Undocumented defaults risk silent misuse. 14 tools accept 'target' but do not specify which default is used or how to override it.