Skip to main content
Glama
Sign In
qidi-mcp

qidi-mcp

by couplet-physical-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

list_webcams

Read-onlyIdempotent

Retrieve available QIDI printer camera feeds and their stream and snapshot URLs to identify which cameras are exposed for monitoring.

Instructions

The cameras this printer exposes, with their stream and snapshot URLs. On stock QIDI firmware the camera is a crowsnest ustreamer instance on port 8080.

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": "list_webcams"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.1

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and idempotentHint, so the safety profile is covered. The description adds useful behavioral context about the returned URLs and the stock QIDI crowsnest ustreamer setup on port 8080.

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 tight sentences, with the core result front-loaded. The firmware-specific sentence is relevant context rather than 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?

With zero parameters, existing annotations, and an output schema, the description covers enough for correct invocation. A little more differentiation from get_webcam_snapshot would make it fully complete.

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?

The tool has zero parameters, so the baseline is 4. The description does not need to explain parameter meanings and appropriately focuses on what the tool returns.

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: it lists the cameras exposed by the printer and mentions stream and snapshot URLs. It is clear what the tool returns, though it does not explicitly contrast with the sibling get_webcam_snapshot.

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?

Usage is implied: an agent can infer this is for discovering camera endpoints before fetching a snapshot. There is no explicit when-to-use guidance or exclusion against get_webcam_snapshot.

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

Deploy Server

Other Tools