Nova

Confirm an expected visitor

confirm_visit

Confirm or reject an expected visitor after verifying who is at the door using the pending signal ID from recent activity.

Instructions

Confirm or reject an expected visitor after checking who is at the door. Ring events alone do not identify people. Use the pending signal ID returned by recent_activity.

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": {
      "signal_id": "<signal_id>",
      "confirmed": "<confirmed>"
    },
    "name": "confirm_visit"
  }
}

Input Schema

Name	Required	Description	Default
`confirmed`	Yes
`signal_id`	Yes

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 24, 2026

TDQS

A3.9/5.0

Behavior3/5

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

Annotations already cover the safety profile (not read-only, not destructive, not idempotent), so the description's main added value is the precondition that a pending signal ID must come from recent_activity and the caveat that ring events don't identify people. It does not describe what happens after confirming vs rejecting (e.g., notifications to the visitor or household), which is meaningful for a decision tool.

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?

Three short sentences with the action and its trigger front-loaded and no padding. The middle sentence about ring events is rationale rather than instruction, but it earns its place by justifying the tool's existence.

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

Completeness4/5

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

For a simple two-parameter tool with an output schema, the description covers the action, the trigger condition, and the dependency on recent_activity. Only the downstream effects of confirming or rejecting are unstated.

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 description coverage is 0%, so the description carries the burden. It explains signal_id well (a pending signal ID from recent_activity) and the confirm/reject phrasing maps onto the boolean confirmed flag, but the semantics of false (reject vs. no-op) are left to inference.

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

Purpose5/5

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

States a specific verb pair (confirm/reject) and resource (an expected visitor), and explains the triggering situation (someone at the door). It also implicitly separates the tool from the sibling that supplies IDs by naming recent_activity as the source of the signal ID.

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

Usage Guidelines4/5

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

"after checking who is at the door" establishes the usage moment, and "Ring events alone do not identify people" warns off a plausible but wrong approach. It points to recent_activity for obtaining the required ID, though it does not explicitly state exclusions such as what to do when no pending signal exists.

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