Nest Protect MCP Server

coordinate_emergency_ai

Coordinate responses to safety incidents by analyzing emergency type and affected devices, using AI sampling to determine response priority and execute actions.

Instructions

Coordinate Emergency AI Response.

Execute intelligent coordination during safety incidents using sampling for complex decisions.

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": {
      "emergency_type": "<emergency_type>",
      "affected_devices": "<affected_devices>"
    },
    "name": "coordinate_emergency_ai"
  }
}

Input Schema

Name	Required	Default
`emergency_type`	Yes
`affected_devices`	Yes
`response_priority`	No	high

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 10, 2026

TDQS

C2.2/5.0

Behavior2/5

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

No annotations are provided, so the description must carry the full burden of behavioral disclosure. It describes 'executing coordination' but does not clarify side effects (e.g., does it send alerts? escalate? mutate state?), required permissions, or any destructive actions. The mention of 'sampling' is ambiguous.

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 two sentences, front-loaded with the title, and contains no filler words. However, the conciseness comes at the cost of clarity; it could be expanded to include key details while remaining efficient.

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 safety-critical tool with 3 parameters and no output schema, the description is severely lacking. It does not explain the tool's process, expected outcomes, or preconditions. Given the complexity of emergency response, the description is grossly incomplete.

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 coverage is 0%, and the description adds no parameter explanations. Parameters like 'emergency_type', 'affected_devices', and 'response_priority' are left undefined; no allowed values or formats are hinted. The description fails to compensate for the lack of schema descriptions.

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

Purpose3/5

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

The description states 'Coordinate Emergency AI Response' which identifies a verb and resource, but is vague. It mentions 'intelligent coordination during safety incidents using sampling for complex decisions' but does not specify what coordination entails or how it distinguishes from siblings like 'hush_active_alarm' or '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 explicit guidance on when to use this tool vs alternatives. The phrase 'during safety incidents' provides vague context but no exclusions or recommendations. Sibling tools overlap significantly without differentiation.

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