Skip to main content
Glama

compatsy 3D printing

Check fit

check_fit
Read-onlyIdempotent

Does this part fit that machine? Returns a verdict with the rule id and version that decided it, or the missing fields. Example: {"subject_id":"e3d-v6-1-75mm-brass-nozzles-0-40mm-1-75mm","target_id":"prusa-mk4s"}

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": {
      "subject_id": "<subject_id>",
      "target_id": "<target_id>"
    },
    "name": "check_fit"
  }
}

Input Schema

NameRequiredDescriptionDefault
target_idYesId or slug of the machine the part goes on
subject_idYesPart id or slug

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / target_id / description
      Previous value: -"Printer or hotend id or slug"New value: +"Id or slug of the machine the part goes on"
  2. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuinely new behavior: it discloses that a verdict is accompanied by the rule id and version that produced it, and that an incomplete call returns the missing fields rather than failing silently. It stops short of explaining how conflicting or ambiguous rules are resolved.

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 sentences plus one example, with the core question front-loaded and the return contract immediately after. Nothing is repeated from the schema and no sentence is wasted.

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 no output schema, the description takes on return-value explanation and does so (verdict, rule id, version, missing fields), which is the right level for a two-parameter read tool. Minor gaps remain around unknown-id handling and the shape of the 'missing fields' response, but nothing essential for correct invocation is absent.

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

Parameters3/5

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

Schema coverage is 100% and both parameters are already documented in the schema, so the schema carries the primary load. The description contributes a concrete example showing realistic slug formats ('prusa-mk4s', a nozzle-style part slug), which hints at expected identifier shape, but it does not describe any format constraints or fallback behavior when a slug is unknown.

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 opens with a specific question-form statement of the operation ('Does this part fit that machine?') that names both the subject (part) and target (machine) of the check, and it states the output (a verdict with rule id and version). It is clearly distinct from siblings like check_stock or compare, 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?

Usage is implied by the question framing — you call it when you need a compatibility decision between a part and a machine — but there is no explicit when-to-use/when-not guidance and no mention of alternatives such as compare or check_stock. An agent can infer the context but gets no routing help.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.