Skip to main content
Glama
mosandlt

Bosch Smart Home Camera MCP Server

by mosandlt

bosch_camera_intercom_open

Open a listen-only audio session to a Bosch camera and retrieve an RTSPS URL for streaming the camera's microphone audio.

Instructions

Open a listen-audio session tunnel to a camera (cloud proxy).

Listen-only — returns an RTSPS URL streaming the camera's microphone audio to the caller. True two-way talk (caller mic -> camera speaker) is not exposed via the Bosch cloud API (same limitation as the Python CLI's own intercom command — it falls back to ffplay for listen-only playback). The returned URL is consumable by ffmpeg/ffplay/VLC; the MCP server does not itself play audio.

Flow: optionally sets the camera's speaker level (full-body PUT to /audio, preserving other fields), then opens a live connection via PUT /v11/video_inputs/{id}/connection (tries REMOTE then LOCAL) and builds an rtsps:// URL with enableaudio=1.

Args: camera: Camera name (case-insensitive). duration: Requested session duration in seconds (embedded in the URL as maxSessionDuration), default 60. speaker_level: Optional 0-100 speaker level to set before opening the session.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cameraYes
durationNo
speaker_levelNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
cameraYesCanonical camera name
durationYesRequested session duration in seconds
rtsps_urlYesCloud-proxy RTSPS URL with enableaudio=1, consumable by ffmpeg/ffplay/VLC
speaker_level_setNoSpeaker level actually applied (0-100), or None if not requested/failed
Behavior5/5

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

With no annotations, the description fully covers behavioral aspects: listen-only limitation, optional speaker level setting, connection flow (REMOTE then LOCAL), and URL construction with enableaudio=1. It also notes the server does not play audio, providing complete transparency.

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 detailed and well-structured with paragraphs and a bullet list of arguments. It is longer than minimal but each sentence adds value. Minor redundancy could be trimmed, but overall effective.

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?

Given the complexity and that output schema exists, the description appropriately explains the return value (RTSPS URL) and the complete workflow. No critical gaps remain for an agent to correctly invoke the tool.

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?

Schema coverage is 0%, yet the description explains each parameter: camera (case-insensitive name), duration (default 60s, embedded as maxSessionDuration), and speaker_level (optional 0-100). It adds practical context beyond the schema, fully compensating for the lack of schema descriptions.

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 clearly identifies the tool as opening a listen-audio session tunnel and returning an RTSPS URL. It explicitly states 'listen-only' and distinguishes from other intercom functions. The verb+resource combination is specific and unambiguous.

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?

The description advises that the tool is listen-only and that true two-way talk is not supported, referencing the Python CLI limitation. It details the intended usage flow but does not explicitly state when to avoid using this tool in favor of siblings, though the context makes it clear.

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/mosandlt/Bosch-Smart-Home-Camera-Tool-MCP'

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