Skip to main content
Glama

screws_tilt_calculate

Probe the Max4 bed's four screw positions and report how far and which direction to turn each levelling knob for manual bed levelling; confirm=true is required.

Instructions

Probe the bed's screw positions and report how far, and which way, to turn each levelling knob. The Max4 has four screws. Manual bed levelling aid — the printer only measures; you turn the knobs. Requires confirm=true.

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

Input Schema

NameRequiredDescriptionDefault
confirmNo
directionNo
confirm_tokenNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.1

TDQS

A3.5/5.0
Behavior4/5

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

Annotations declare readOnlyHint=false, idempotentHint=false, destructiveHint=false, and the description adds real context beyond them: the operation only measures, the human performs the physical adjustment, and confirm=true is required. It does not explain what confirm_token is for or what happens if confirm is omitted, which keeps it short of a 5.

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?

Three short sentences, front-loaded with the action and result, then the manual-vs-automatic clarification, then the prerequisite. No filler.

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 not be described, and the core behavior is clear. However, for a tool with a confirm/confirm_token safety gate, the description leaves two of three parameters undocumented, which is a meaningful gap for correct invocation.

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?

Schema description coverage is 0% across three parameters, and the description only covers one of them (confirm=true). The 'direction' and 'confirm_token' parameters are left entirely unexplained in both schema and description, so an agent cannot infer their meaning or valid values.

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?

States a specific verb and resource: probe the bed's screw positions and report how far and which way to turn each levelling knob. The 'manual bed levelling aid — the printer only measures; you turn the knobs' clause separates it from automatic routines like z_tilt_adjust or bed_mesh_calibrate, though it never names those siblings explicitly.

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?

The description implies the usage context (manual levelling, agent must turn knobs) and states the confirm=true prerequisite, but it gives no explicit when-to-use/when-not guidance against the many other levelling tools in the sibling list (z_tilt_adjust, bed_mesh_calibrate, qidi_bed_level_calibrate).

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