Skip to main content
Glama
Sign In
thermoslop

thermoslop

by martellj
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

get_status

Read-only

Retrieve temperature, humidity, HVAC mode and comfort settings for one thermostat, a house, or all thermostats, using cached readings or live data on request.

Instructions

Current temperature, humidity, HVAC mode and action, setpoints, comfort setting (home/away/sleep, or 'hold' for a manual hold) and remote sensors, in each thermostat's own units (units). With no arguments, covers every thermostat.

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_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
liveNoAsk the thermostats instead of using the recent cached reading.
houseNoOnly thermostats in this house, e.g. 'cabin'.
thermostatNoThermostat alias or name prefix, e.g. 'upstairs'. See list_thermostats.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already establish readOnlyHint=true and openWorldHint=false, so the description only needs to add operational context. It clarifies that all thermostats are covered by default and that values are reported in each thermostat's own units, but it does not mention the live-versus-cached behavior that meaningfully affects results.

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?

The description is compact and front-loads the returned information, with the default coverage note placed at the end. The field list is lengthy but relevant, and there is no filler.

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?

With a complete input schema, an output schema, and read-only annotations, the definition gives enough context to call the tool correctly. The remaining gap is that the description does not discuss the live/cache distinction, though that is handled in the schema.

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 description coverage is 100%, so the schema already documents live, house, and thermostat. The description adds only the default all-thermostats behavior and the units detail; it does not add syntax or filtering nuances beyond what the schema provides.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific resource and enumerates the status fields returned: temperature, humidity, HVAC mode/action, setpoints, comfort setting, and remote sensors. It is clearly a read-status tool, distinguishable from the set_* siblings, though it does not explicitly distinguish itself from list_thermostats.

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?

The only usage cue is "With no arguments, covers every thermostat," which implies broad reads and scoped reads via filters. There is no explicit guidance on when to use this versus list_thermostats or when to prefer live versus cached readings, leaving those decisions to the schema.

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