Home Assistant MCP Server

Overview Schema Source Related Servers Discussions Admin

Get a camera or image snapshot

get_camera_snapshot

Read-onlyIdempotent

Fetches the current image from a Home Assistant camera or image entity and returns it as an image for direct viewing, including off or black camera feeds.

Instructions

Fetch the current picture from a camera or image entity and return it as an image, so it can be looked at directly. Cameras that are off or show black in the UI will return that too. Limited to 4 MB.

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": {
      "entity_id": "<entity_id>"
    },
    "name": "get_camera_snapshot"
  }
}

Input Schema

Name	Required	Description	Default
`entity_id`	Yes	A camera.* or image.* entity.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.1Nov 5, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely useful behavior beyond that: cameras that are off or render black still return that output, and responses are capped at 4 MB.

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, front-loaded with what is fetched and returned, then the two caveats. Slightly loose in 'so it can be looked at directly', but no sentence is wasteful.

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?

There is no output schema, but the description states the return is an image and covers the two realistic edge cases (off/black cameras, 4 MB cap). Behavior on an invalid or missing entity is left unstated, which is the only notable gap for a one-parameter tool.

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 100% and the single entity_id parameter already documents the camera.* or image.* entity types. The description adds nothing new about the parameter (no ID format examples or error behavior for an unknown entity), so the baseline applies.

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 (fetch) and resource (current picture from a camera or image entity), plus the return form (an image, viewable directly). No sibling tool in the list does image retrieval, so there is no ambiguity to resolve.

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

Usage Guidelines3/5

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

The phrase 'so it can be looked at directly' implies the use case, but there is no explicit when-to-use framing, no mention of when to prefer get_entity_details or state queries, and no prerequisites such as entity availability. Usage is inferable rather than stated.

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