mcp-server-qidi

Webcam snapshot

qidi_snapshot

Read-onlyIdempotent

Capture a chamber webcam image to verify the build plate is empty before printing or inspect a running print; enable the chamber light first for a visible picture.

Instructions

Take a picture with the chamber webcam. Use it to check that the build plate is empty before starting a print, or to look at a running print. Set light=true to switch the chamber light on first (needs the control tier); the picture is dark without it.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "qidi_snapshot"
  }
}

Input Schema

Name	Required	Description	Default
`light`	No	Switch the chamber light on before taking the picture.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 7, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive behavior, and the description adds real operational context: the light flag requires the control tier and the image is dark without it. It stops short of saying what is returned (raw image vs. a path/URL), which is the one meaningful gap for a snapshot 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?

Three tightly packed sentences: action first, then usage scenarios, then the parameter caveat. Nothing is redundant and the most decision-relevant facts are front-loaded.

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 single-flag, read-only tool with no output schema, the description covers purpose, when to call it, and the key parameter caveat. Only the shape of the returned image is unstated, a minor omission given the tool's simplicity.

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 coverage is 100% and already documents the light flag, yet the description still adds value by disclosing the permission tier it requires and the consequence of omitting it ('the picture is dark without it').

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 concrete verb and resource ('Take a picture with the chamber webcam') that no sibling tool covers, and the scope is unambiguous against qidi_set_light and the status tools.

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?

Supplies two explicit scenarios: verifying the build plate is empty before a print, and inspecting a running print. It does not spell out when not to call it, but the positive cases are concrete enough to route an agent correctly.

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

Deploy Server