ipcam-mcp

Overview Schema Source Related Servers Discussions Admin

Record every camera in a scene

scene_record

Record a synchronized 1–60 second video clip from every camera in a scene, with each file labeled by camera name. Returns file paths and sizes, not the videos.

Instructions

Record a video clip (1-60 s) with every camera in the scene at the same time, labelled with the camera's name. Returns each file's path and size, not the video.

quality: "high" = main stream (full resolution set on the camera); "low" = sub stream (smaller file).

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": {
      "scene": "<scene>"
    },
    "name": "scene_record"
  }
}

Input Schema

Name	Required	Default
`scene`	Yes
`quality`	No	high
`seconds`	No

Schema Changelog

Changes observed during successful MCP inspections.

Addedv0.5.1Nov 10, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations declare readOnlyHint=false and destructiveHint=false but nothing about output; the description fills that gap by stating it returns each file's path and size rather than the video, and explains the duration bound and stream trade-off. It does not mention where files land or whether repeated calls overwrite, which is the main remaining gap.

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?

Three short sentences, front-loaded with the action and scope, followed by the return contract and the enum semantics. Every sentence carries distinct information with no restatement of the title or name.

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?

With no output schema, the description correctly supplies the return shape (file paths and sizes) plus the quality trade-off and duration limits. A note on the scene identifier format and output location would make it complete for a multi-camera capture tool.

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

Parameters4/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 and does well: it defines the 1-60 s duration and unpacks the high/low enum into main stream (full resolution) vs sub stream (smaller file). Only the required "scene" parameter's accepted form (name vs. identifier) is left unaddressed.

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 video clip") scoped to "every camera in the scene at the same time," which immediately distinguishes it from the single-camera camera_record sibling and from the non-video scene_snapshot. An agent can tell what it produces (files, not footage) without opening the schema.

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 description makes the use case implied — simultaneous recording across all cameras in a scene — but never explicitly says when to prefer this over camera_record or scene_snapshot, nor states prerequisites. Adequate but leaves alternative selection to inference.

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