Skip to main content
Glama
Sign In
HomeLab MCP

HomeLab MCP

by chip10
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

ha_turn_off

Turn off any smart home entity by specifying its entity ID and confirming the action. Enables remote device control with a required confirmation step.

Instructions

Apaga una entidad.

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": {
      "entity_id": "<entity_id>",
      "confirm": "<confirm>"
    },
    "name": "ha_turn_off"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmYes
entity_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.9/5.0
Behavior1/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only states the action without revealing side effects, reversibility, confirmation requirements, or what the confirm parameter does. The behavior beyond the action is entirely opaque.

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 terse—a single line. While concise, it under-specifies essential information. Conciseness should not sacrifice clarity, and the short length here is more a symptom of under-specification than efficient writing.

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

Completeness1/5

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

For a tool with two required parameters and no output schema or annotations, the description is grossly incomplete. An agent cannot determine how to populate confirm, what the expected outcome is, or any error conditions. The coverage is inadequate for correct invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must explain the parameters. It does not mention entity_id or confirm at all, leaving the agent to infer meaning solely from names. This is a significant gap given the required confirm parameter.

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 'Turns off an entity' clearly states the verb (turn off) and the resource (entity), which is distinct from the sibling tools like ha_turn_on. However, it does not specify what type of entity or differentiate from generic actions like ha_call_service. The purpose is clear at a high level but lacks sibling differentiation.

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

Usage Guidelines1/5

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

The description provides no guidance on when to use this tool versus alternatives such as ha_call_service or ha_turn_on. There is no mention of context, exclusions, or prerequisites. An agent receives no help in selecting this tool over its siblings.

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