Skip to main content
Glama
Sign In
qidi-mcp

qidi-mcp

by couplet-physical-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get_position

Read-onlyIdempotent

Retrieve the 3D printer toolhead position, including raw kinematic and G-code coordinates, homed axes, active Z offset, plus speed and flow factors.

Instructions

Toolhead position: raw kinematic position, the G-code position (offsets applied), which axes are homed, the active Z offset, and speed/flow factors.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.1

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 destructiveHint=false, so the safety profile is covered. The description adds genuine behavioral context by distinguishing raw kinematic coordinates from G-code coordinates with offsets applied, and by disclosing that homing state, Z offset, and speed/flow factors are bundled in. It does not mention units, coordinate frame conventions, or timing/polling behavior.

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 dense sentence with zero filler, and the core resource is front-loaded before the field enumeration. It is telegraphic (a colon-led list rather than a sentence), which is efficient but slightly less readable than a full clause.

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?

With an output schema present, the description need not spell out return structure, and the field list it does give is enough to know what an agent gets back. For a zero-parameter read tool with full annotation coverage, the remaining gap — no units or usage routing — is minor.

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 there is nothing for the description to disambiguate beyond what the empty schema shows. The baseline of 4 applies; no parameter meaning is missing.

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 precisely (toolhead position) and enumerates the exact data groups returned: raw kinematic position, G-code position with offsets applied, homed axes, active Z offset, and speed/flow factors. This clearly distinguishes it from sibling readers like get_printer_status or get_temperatures, though it uses a noun fragment rather than a verb+resource phrasing.

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 guidance on when to call this versus alternatives such as get_printer_status or query_objects, and no stated preconditions. The only hint is implicit in the returned fields — an agent must infer that this is the tool for coordinate/homing checks.

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