qidi-mcp

display_message

Idempotent

Display a short message on the printer screen and optionally write it to the G-code console so Fluidd viewers can see status or alerts.

Instructions

Show a short message on the printer's screen (M117) and/or write one to the G-code console (M118), which is where a human watching Fluidd will see it.

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": {
      "message": "<message>"
    },
    "name": "display_message"
  }
}

Input Schema

Name	Required	Description	Default
`message`	Yes
`to_console`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.0.1Nov 9, 2026

TDQS

A3.9/5.0

Behavior3/5

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

Annotations already declare it is not read-only but is idempotent and non-destructive; the description adds useful context about which G-code commands are sent and where the output surfaces (Fluidd console). It does not say whether the screen message is transient or how it is cleared, nor what the response contains (an output schema exists).

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 front-loaded sentence with the action first and the clarifying parenthetical second; nothing is redundant. The final relative clause about Fluidd is slightly verbose but still earns its place by explaining visibility.

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 two-parameter, low-complexity tool with an output schema covering returns, the description is nearly sufficient: it conveys the effect, the mechanism, and the audience. Only minor gaps remain (message length, whether the screen message persists).

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 0%, so the description must carry the parameters, and it does: "short message" characterizes the message string and the "and/or" phrasing explains that to_console independently toggles writing to the G-code console. It stops short of stating any length limit or default behavior for to_console.

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 ("Show a short message on the printer's screen") and names the underlying G-code commands M117/M118, which pins down exactly what the tool emits. An agent can distinguish this from read/control siblings without opening the schema.

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 only implied: the note that the console is "where a human watching Fluidd will see it" clarifies the intent of notifying an operator. There is no explicit when-to-use/when-not guidance or routing to an alternative (e.g., logging tools such as get_gcode_log).

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

Deploy Server