Skip to main content
Glama
tim661811
by tim661811

Outdoor weather

homey_weather
Read-onlyIdempotent

Fetch the outdoor weather Homey uses, including current temperature, humidity, pressure, sky description, and forecast, to compare with indoor sensors or plan activities.

Instructions

Reads the outdoor weather Homey itself uses: temperature, humidity, air pressure, a readable sky description, and the name of the town the reading is for, plus the forecast, in one call. Use it to compare outdoors against indoors (pair it with homey_device_get on a room sensor), to answer whether opening a window would help, or to look ahead to tonight's low. Humidity is returned as a percentage from 0 to 100: Homey's own field is a 0 to 1 fraction and is converted here. Temperature is in whatever unit this Homey is configured for, echoed as temperatureUnits, and pressure is given in bar with the millibar (hectopascal) equivalent beside it. Forecast granularity depends on the hardware and is stated explicitly in every result: a daily forecast is always returned, each day carrying its expected, minimum and maximum temperature, where the minimum is effectively that night's low, while an hourly forecast is included only when this Homey offers one and its absence is reported as a plain statement rather than as an error. What it cannot do: it is one reading for one location, the town it names, taken from Homey's weather provider rather than from any hardware in this house, so it is not a substitute for an outdoor sensor in the garden and says nothing about conditions in any individual room. The sky description arrives in the Homey's own language. For outdoor history rather than the present, look for the logs owned by homey:manager:weather with homey_insights_search and query those.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
includeForecastNoInclude the forecast as well as the current conditions. On by default; turn it off for just the reading.
includeHourlyForecastNoInclude an hourly forecast when this Homey has one. On by default. Turning it off skips the extra request on hardware where the hourly forecast is a separate route.
Install Server

TDQS

A4.4/5.0
Behavior5/5

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

The description transparently explains output units and conversions (humidity percentage, temperature unit, pressure bar/millibar), forecast granularity dependence on hardware, and that sky description is in the Homey's language. It also mentions the absence of hourly forecast and that it's a single reading for one location. This aligns with the read-only and idempotent annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is overly verbose and repetitive, repeating the same clarifications multiple times, such as the explanation of units and limitations. While it is structured, the redundancy detracts from conciseness.

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?

The description provides comprehensive context, including relationship to other tools, limitations, and data specifics. It covers all necessary aspects for a user to understand and use the tool effectively, including when not to use it.

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?

The input schema provides clear descriptions for the two boolean parameters (includeForecast and includeHourlyForecast), including defaults and use cases. The tool description does not add additional parameter explanation, but the schema coverage is complete, so the baseline of 3 is appropriate.

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 clearly states that the tool reads outdoor weather from Homey, listing specific data fields (temperature, humidity, air pressure, sky description, town name) and mentions the forecast. It also differentiates it from other tools by specifying it's the weather Homey itself uses and suggests pairing with indoor sensor tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides explicit use cases: comparing outdoor to indoor (pairing with homey_device_get), answering if opening a window helps, and looking ahead to tonight's low. It also notes limitations, such as not being a substitute for an outdoor sensor and directing history queries to homey_insights_search.

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

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/tim661811/homey-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server