Skip to main content
Glama
Sign In
thermoslop

thermoslop

by martellj
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

set_mode

Idempotent

Change the HVAC mode to heat, cool, or auto for a selected thermostat or house; off is disabled on this server.

Instructions

Set the HVAC mode. 'off' is disabled on this server.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "mode": "<mode>"
    },
    "name": "set_mode"
  }
}

Input Schema

NameRequiredDescriptionDefault
modeYes
houseNoOnly thermostats in this house, e.g. 'cabin'.
thermostatNoThermostat alias or name prefix, e.g. 'upstairs'. See list_thermostats.

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 declare readOnlyHint=false, idempotentHint=true and destructiveHint=false, so the mutation/idempotency profile is covered. The description adds real value by disclosing that one enum value is rejected by this server, but it says nothing about whether the change creates a hold, clears a schedule, or applies to all thermostats when the optional filters are omitted.

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

Conciseness5/5

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

Two short sentences, no filler, and the operational constraint is front-loaded right after the purpose statement. Nothing is redundant with the schema or annotations.

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

Completeness3/5

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

With only 'mode' required, the important question is what happens when 'house' and 'thermostat' are null — presumably all thermostats change — and that scoping behavior is never stated. No output schema exists, so the description also leaves the result (success, partial failure across multiple thermostats) unexplained.

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 67%: 'house' and 'thermostat' are documented in the schema, while 'mode' is only an enum list. The description adds meaning to 'mode' by flagging that 'off' is unavailable despite being in the enum, which is a genuine gap-filler, but the house/thermostat omission semantics remain undocumented. Baseline 3 fits.

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?

States a specific verb and resource ('Set the HVAC mode'), which is unambiguous against siblings like set_temperature or resume_schedule because it names 'mode' as the target. It does not explicitly contrast itself with those siblings, but no reasonable agent would confuse the two.

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 guidance is the constraint that 'off' is disabled on this server, which is a useful exclusion and saves a failed call. There is no stated when-to-use context versus set_comfort / resume_schedule, and no prerequisites such as permissions or whether the change overrides an active schedule.

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