set_presenceUpdate your home presence and sleep state to control automations. Set home/away and awake/asleep status to trigger presence-based automation rules.
Set your own presence (home/away) or sleep state (awake/asleep). This affects presence-based automations.
| Name | Required | Description | Default |
|---|---|---|---|
| asleep | No | true = asleep, false = awake | |
| present | No | true = home, false = away |
Changes observed during successful MCP inspections.
v2.1.1Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare non-read-only, idempotent, and non-destructive. The description adds behavioral context beyond annotations by explaining that this affects presence-based automations, which is valuable for understanding consequences. No contradiction with annotations.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two concise sentences front-load the purpose and then add the important consequence. No wasted words, every sentence serves a clear purpose.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the simple tool with two optional boolean parameters, strong annotations, and full schema descriptions, the description covers the essential selection and invocation context. It could mention what happens if both parameters are omitted, but this is not critical for basic usage.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, with both parameters (asleep and present) fully described. The description adds high-level meaning by framing them as 'presence (home/away)' and 'sleep state (awake/asleep)', but this largely restates the schema, so baseline 3 is appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states it sets presence (home/away) or sleep state (awake/asleep), using a specific verb and resource. This distinguishes it from sibling tools like get_presence and other set_ tools.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies when to use this tool: to set your own presence or sleep state, and notes that it affects automations. While it doesn't explicitly list alternatives or exclusions, the context is unambiguous given the sibling tool names.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.