Agent Cam MCP Tool

save_baseline

Capture a golden reference image for later comparison, establishing a known-good baseline before running experiments or flashing firmware.

Instructions

Capture and persist a golden reference image for subsequent comparison. Use to establish a known-good baseline before running experiments or flashing firmware.

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

Input Schema

Name	Required	Description
`name`	Yes	Baseline name
`camera`	No	Camera ID
`region`	No	Optional named region to save as baseline

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 4, 2026

TDQS

A3.8/5.0

Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It discloses that the image is persisted and that it becomes a 'known-good' reference, which is useful context. However, it says nothing about overwrite behavior when a baseline of the same name exists, required permissions, or side effects on existing baselines – significant gaps for a persist/mutation tool.

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?

Two sentences, zero waste. The core action and scope are front-loaded, with the usage hint following immediately. Nothing needs trimming.

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?

For a simple 3-param persist tool with no output schema and no annotations, the description covers purpose and timing well. The remaining gap is the absence of overwrite/side-effect semantics, which matters for a save operation but is a modest omission here.

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% with three documented params (name, camera, region), so the schema already carries parameter meaning. The description adds no syntax, defaults, or format details beyond it, making the baseline 3 correct.

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?

States a specific verb+resource: 'Capture and persist a golden reference image for subsequent comparison.' The phrase 'golden reference... for subsequent comparison' implicitly separates it from capture_image and points toward compare_to_baseline. It stops short of naming a sibling explicitly, so it lands at 4 rather than 5.

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 a clear trigger: 'Use to establish a known-good baseline before running experiments or flashing firmware.' That tells the agent when this tool is appropriate. It does not state when NOT to use it or name an alternative, so it is a clear-context 4, not a 5.

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