Skip to main content
Glama
Fistacho

ha-nexus-agent

by Fistacho
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Record a camera clip

services_camera_record
DestructiveIdempotent

Record a short video clip from a camera entity and save it to a file, overwriting any existing file. Use for capturing motion or events instead of a single still frame.

Instructions

Record a short clip from a camera entity to a file, overwriting any existing file at that path.

Calls camera.record with {"entity_id": entity_id, "filename": filename, "duration": duration} over HTTP.

Use when: capturing a short video clip rather than a single still frame. Not for: a single still frame — use services_camera_snapshot. Returns: dict with entity_id, filename, duration and the raw service call result. Limits: blocks for roughly duration seconds while HA records.

Input Schema

NameRequiredDescriptionDefault
durationNoRecording length in seconds.
filenameYesDestination path inside the HA config directory, e.g. '/config/www/snapshots/clip.mp4'. Overwrites any existing file there.
entity_idYesFull camera entity ID to record, e.g. 'camera.front_door'.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.25.1
    • addedInput schema / properties / duration / description
      Added value: +"Recording length in seconds."
    • addedInput schema / properties / entity_id / description
      Added value: +"Full camera entity ID to record, e.g. 'camera.front_door'."
    • addedInput schema / properties / filename / description
      Added value: +"Destination path inside the HA config directory, e.g. '/config/www/snapshots/clip.mp4'. Overwrites any existing file there."
  2. First observedv0.3.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, idempotentHint=true and readOnlyHint=false, so the safety profile is covered; the description reinforces it with 'overwriting any existing file' and adds genuinely new context — that the call blocks for roughly `duration` seconds. It does not discuss error/auth behavior, so it falls short of a 5.

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?

Front-loaded with the action, then neatly labeled Use/Not for/Returns/Limits sections — good scannability. The raw `camera.record` JSON payload line largely restates the schema and is the one element that doesn't fully earn its place.

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

Completeness5/5

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

For a 3-param mutation tool with an output schema, the description covers purpose, alternative routing, destructive overwrite behavior, blocking semantics and return shape. Nothing an agent needs to invoke it correctly is missing.

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 coverage is 100%, so all three parameters are already documented in the schema. The description repeats them in the underlying service payload but adds no syntax or format detail beyond what the schema provides; baseline 3 is appropriate.

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 and resource ('Record a short clip from a camera entity to a file') and immediately distinguishes itself from the still-frame sibling by naming services_camera_snapshot. An agent can route correctly without opening either schema.

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

Usage Guidelines5/5

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

Explicit 'Use when' (capturing a short video clip) and 'Not for' (single still frame — use services_camera_snapshot) sections. The alternative and the condition that selects it are both named.

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