ipcam-mcp

Overview Schema Source Related Servers Discussions Admin

Scene timeline

scene_timeline

Read-only

Retrieves snapshots, recordings, and baselines for a scene from every camera that watched it, newest first, with date-range filters for reviewing change over time.

Instructions

The scene's snapshots, recordings and baselines, newest first, from every camera that watched it (removed ones too). start/end: YYYY-MM-DD (whole day) or an ISO datetime. limit: 1-500 entries. Open a snapshot with camera_snapshot(from_path=...).

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_timeline"
  }
}

Input Schema

Name	Required	Description	Default
`end`	No
`limit`	No
`scene`	Yes
`start`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv0.5.1Nov 10, 2026
- addedInput schema / properties / limit / maximum
```
Added value: +500
```
- addedInput schema / properties / limit / minimum
```
Added value: +1
```
First observedv0.4.1Nov 6, 2026

TDQS

A3.9/5.0

Behavior3/5

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

With readOnlyHint=true and openWorldHint=false already covering safety, the description adds real behavioral detail: results span every camera including removed ones, and ordering is newest first. It does not explain truncation or pagination behavior when limit is reached, which for a listing tool is the remaining meaningful 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 compact sentences, front-loaded with what the result is and how it is ordered, then parameter syntax, then the follow-up call. No sentence is filler.

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?

An output schema exists so return content needn't be described, and the description covers ordering, cross-camera scope including removed cameras, date semantics, and the limit range. It is nearly complete for a read-only listing tool, missing only what happens when results exceed the limit.

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 must carry parameter meaning and it largely does: both date formats for start/end, the 1-500 bound and default-ish behavior for limit, and the scene linkage via 'The scene's'. The scene identifier's expected format is still unspecified, keeping it from a 5.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Names the exact resource set returned (snapshots, recordings and baselines) for a scene, with the scope 'from every camera that watched it (removed ones too)' and the ordering 'newest first'. That is far more specific than a restatement of the title, though it never states a verb (list/retrieve) and doesn't contrast itself with siblings like scene_compare or scene_record.

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?

Gives concrete usage guidance: start/end accept whole-day YYYY-MM-DD or an ISO datetime, limit is bounded 1-500, and the follow-up action 'Open a snapshot with camera_snapshot(from_path=...)' is spelled out. It still gives no when-not guidance or prerequisites, so it stops short of a 5.

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