Nest Protect MCP Server

configure_smart_automation

Configure adaptive automation rules that learn from your lifestyle patterns to enhance proactive safety.

Instructions

Configure Smart Safety Automation.

Set up adaptive automation rules that learn your lifestyle patterns for proactive safety.

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": {
      "automation_type": "<automation_type>"
    },
    "name": "configure_smart_automation"
  }
}

Input Schema

Name	Required	Default
`automation_type`	Yes
`learning_period`	No	2_weeks
`confidence_threshold`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 10, 2026

TDQS

C2.4/5.0

Behavior2/5

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

No annotations are present, so the description carries full burden. It only states a high-level behavior (adaptive learning) but does not disclose side effects, idempotency, or safety considerations.

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

Conciseness3/5

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

The description is short and front-loaded but sacrifices necessary detail. It is concise but under-informative for an agent to use effectively.

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

Completeness2/5

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

Given 3 parameters, no output schema, and no annotations, the description is insufficient. It does not cover return values, configuration effects, or behavior when called multiple times.

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% and the tool description adds no explanation for any parameter. The agent cannot determine valid values for automation_type, meaning of learning_period, or the range of confidence_threshold.

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?

Description clearly states the tool configures smart safety automation and mentions it learns lifestyle patterns for proactive safety. However, it does not specify what automation types are available, which diminishes differentiation from sibling tools like set_security_mode.

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

Usage Guidelines2/5

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

No guidance on when to use this tool versus alternatives. No prerequisites or context provided, leaving the agent to infer usage from the vague description.

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