Skip to main content
Glama
Sign In
qidi-mcp

qidi-mcp

by couplet-physical-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

set_case_light

Idempotent

Turn the 3D printer chamber light on or off to illuminate the build area before taking a webcam snapshot.

Instructions

Turn the chamber/case light on or off. Handy before taking a webcam snapshot.

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

Input Schema

NameRequiredDescriptionDefault
onYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.1

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare this is a non-read-only, idempotent, non-destructive operation, so the safety profile is covered. The description adds little beyond that: it does not say whether the light state persists, whether it affects any other output, or which physical channel it drives relative to set_led.

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 short sentences, action first, rationale second. Nothing is padded and the purpose is 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 one-parameter toggle with annotations and an output schema, this is close to complete: the agent knows what it does, what the argument means, and a situation in which to call it. Only the relationship to the sibling set_led remains unspecified.

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 single required boolean 'on' has no schema description, but "turn ... on or off" makes the true/false meaning unambiguous. With only one parameter and its polarity spelled out, the description compensates adequately for the 0% schema coverage.

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 and resource: turning the chamber/case light on or off. That is clear enough to act on, though it does not differentiate itself from the sibling set_led, so an agent may have to guess which light control applies.

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?

"Handy before taking a webcam snapshot" gives an implied usage context that ties it to get_webcam_snapshot, but there is no explicit when-not guidance and no mention of set_led as the alternative for other lighting.

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