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

mcp-server-qidi

by borgels
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

QIDI Box status

qidi_box_status
Read-onlyIdempotent

Retrieve filament details for each QIDI Box slot—vendor, material, color, insertion status—plus the loaded slot, humidity, temperature, and drying state.

Instructions

Filament in each QIDI Box slot (vendor, material, colour, whether filament is inserted), which slot is loaded, box humidity, temperature and drying state.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and non-destructive behaviour, so the safety profile is fully covered without the description. What the description adds is the content of the read (humidty, temperature, drying state, per-slot filament data), which is useful but sits closer to return-value documentation than to behavioural disclosure. It says nothing about refresh behaviour, staleness, or what happens when no box is attached.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single tight sentence with the resource stated first and the enumerated fields following; no filler and no redundancy. The only structural weakness is that it is a fragment rather than a declarative clause, which reads slightly awkwardly as a tool description.

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?

There is no output schema, so the description must stand in for the return shape, and it does list the key fields an agent would need to interpret the response. It stops short of describing nesting or how slots are keyed/ordered, which an agent would still have to discover at call time.

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?

With zero parameters and a 100% covered (empty) schema, there is nothing for the description to disambiguate. The baseline of 4 applies unchanged.

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?

The description names the resource (a QIDI Box) and enumerates exactly what status is surfaced: per-slot filament vendor/material/colour/insertion, loaded slot, humidity, temperature and drying state. That is specific enough to separate it from qidi_printer_status and qidi_server_status. It loses a point only because it is a noun-phrase fragment with no explicit verb ('returns'/'gets').

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use guidance, no mention of alternatives, and no note that this is the box-specific counterpart to qidi_printer_status. The zero-parameter, read-only nature makes misuse unlikely, so the gap is tolerable but real.

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