Skip to main content
Glama
Sign In
mcp-server-qidi

mcp-server-qidi

by borgels
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Pause print

qidi_pause_print
Idempotent

Pause a running QIDI 3D print and park the nozzle; resume printing with the matching resume tool.

Instructions

Pause the running print (the printer parks the nozzle). Resume with qidi_resume_print.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare non-read-only, idempotent, non-destructive semantics, and the description adds a concrete physical consequence — the nozzle parks — which tells the agent the machine moves when called. It does not explain what happens to an in-progress job's state beyond the pause, or any preconditions such as a print actually running.

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?

A single sentence, front-loaded with the action and followed by the physical effect and the resume path. No wasted wording and nothing important buried.

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 parameterless printer-control action, the description plus annotations give enough to call it correctly and to know the exit path. It is slightly thin on preconditions (must a print be running?) and on what the call returns, though no output schema exists to cover that.

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 takes zero parameters, so the baseline applies; there is nothing parameter-level the description needs to compensate for. The schema is empty and fully consistent with the description.

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 specific verb and resource ("Pause the running print") with the added physical detail that the printer parks the nozzle. It also names the complementary sibling qidi_resume_print, so the agent can distinguish it from cancel or emergency stop.

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?

It explicitly tells the agent how to reverse the action (resume with qidi_resume_print), which is the main routing decision for this tool. It does not state when to prefer qidi_cancel_print or qidi_emergency_stop over pausing, so a destructive-alternative exclusion is missing.

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