qidi-mcp

get_bed_mesh

Read-onlyIdempotent

Retrieves the active bed mesh and saved profiles, including the probed Z-deviation grid, range, and mesh area, to reveal whether the print bed is warped and by how much.

Instructions

The active bed mesh and saved profiles: the probed Z deviation grid, its range, and the mesh area. Reveals whether the bed is warped and by how much.

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

Input Schema

Name	Required	Description	Default
`include_matrix`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.0.1Nov 9, 2026

TDQS

B3.3/5.0

Behavior3/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 content scope (active mesh plus stored profiles, range, area) but says nothing about behavior when no mesh exists or about response size when the full matrix is requested.

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, front-loaded with what is returned and closed with the practical interpretation. No filler or repetition of the tool name.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return values need no explanation, and the tool is simple. However, the undocumented include_matrix parameter leaves the agent without guidance on payload size, which is a meaningful gap for a mesh-grid tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

There is one parameter, include_matrix, with 0% schema description coverage, and the description never mentions it. That flag likely controls whether a large grid payload is returned, which is exactly the kind of meaning the description should supply; it does not compensate for the coverage gap.

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 a specific resource and enumerates its contents: 'the probed Z deviation grid, its range, and the mesh area', plus saved profiles. It is clearly a read operation, distinct from bed_mesh_calibrate. The only ambiguity is the mention of 'saved profiles', which overlaps with the sibling bed_mesh_profile, so it isn't a perfect sibling separation.

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?

'Reveals whether the bed is warped and by how much' implies the diagnostic use case but never states when to pick this over bed_mesh_calibrate, bed_mesh_profile, or screws_tilt_calculate. Usage is inferable rather than stated, and no exclusions or prerequisites are given.

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

Deploy Server