Skip to main content
Glama
homeassistant-ai

Home Assistant MCP Server

Official

Get Camera Image

ha_get_camera_image
Read-onlyIdempotent

Fetch a live camera snapshot from Home Assistant to verify security, check on pets, or confirm deliveries. Returns the image for visual analysis.

Instructions

Retrieve a snapshot image from a Home Assistant camera entity.

This tool fetches the current camera image and returns it directly for visual analysis. Use this when you need to see what a camera is currently viewing.

Parameters:

  • entity_id: Camera entity ID (e.g., 'camera.front_door', 'camera.living_room')

  • width: Optional width to resize the image (reduces token usage for large images)

  • height: Optional height to resize the image

Use Cases:

  • Security checks: "Is someone at the front door?"

  • Pet monitoring: "Is my dog still on the couch?"

  • Delivery verification: "Did my package get delivered?"

  • Visual confirmation: "Did the garage door actually close?"

  • Incident investigation: "What triggered the motion sensor?"

Example Usage:

# Get current snapshot from front door camera
ha_get_camera_image(entity_id="camera.front_door")

# Get resized image to reduce token usage
ha_get_camera_image(entity_id="camera.backyard", width=640, height=480)

Notes:

  • Only cameras exposed to Home Assistant are accessible

  • The existing HA authentication/authorization applies

  • Images are returned in their native format (JPEG, PNG, or GIF)

  • Use width/height parameters for large high-resolution cameras to reduce token usage when full resolution is not needed

Related Services:

  • camera.snapshot: Save snapshot to file on HA server

  • camera.turn_on/turn_off: Control camera power

  • camera.enable_motion_detection: Enable motion detection

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
widthNo
heightNo
entity_idYes
Behavior5/5

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

Annotations already declare readOnlyHint=true and idempotentHint=true. The description adds further behavioral detail: images are returned in native format, token usage can be reduced via width/height, and only cameras exposed to HA are accessible. No contradictions.

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

Conciseness5/5

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

Well-structured with sections: description, parameters, use cases, example, notes, related services. Front-loaded with main purpose. Every sentence adds value—no fluff.

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?

Despite no output schema, description explains return format (JPEG/PNG/GIF), authentication, camera availability, and token optimization. Covers all essential aspects for correct invocation and expectation setting.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Input schema has 0% parameter description coverage, so the description must compensate. It lists all three parameters with explanations (entity_id format, width/height purpose to 'reduce token usage') and provides example values inline, greatly enriching the schema.

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?

The description opens with a clear verb+resource: 'Retrieve a snapshot image from a Home Assistant camera entity.' It specifies the exact action and target, and given the sibling list includes many other HA tool types, this tool is well-distinguished as the only one focused on camera snapshots.

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?

Provides explicit use cases (security, pet monitoring, etc.) and example usage with code. Also lists 'Related Services' that contrast with this tool (e.g., camera.snapshot saves to file), giving the agent clear when-to-use and when-not-to-use guidance.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/homeassistant-ai/ha-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server