MCP 3D Printer Server

center_model

Translate an STL model so its geometric center sits at the origin (0,0,0), aligning it for slicing or print preparation.

Instructions

Translate the model so its geometric center is at the origin (0,0,0).

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": {
      "stl_path": "<stl_path>"
    },
    "name": "center_model"
  }
}

Input Schema

Name	Required	Description	Default
`stl_path`	Yes	Path to the STL file to center.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.2.9Sep 29, 2026

TDQS

B3.1/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It says the tool translates the model, but does not state whether it modifies the file in place, returns a new file, requires write permissions, or what side effects occur.

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?

The description is a single, front-loaded sentence that specifies the operation and the target result with no wasted words.

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?

For a simple one-parameter tool, the description adequately conveys the core action. However, without annotations or an output schema, it leaves open important behavioral details such as whether the original STL is modified or a new file is produced.

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 description coverage is 100%, and the single stl_path parameter is fully documented in the schema. The description adds no parameter-level meaning beyond the schema, so the baseline of 3 is appropriate.

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 uses a specific verb ('Translate') and states the exact geometric outcome: centering the model at the origin (0,0,0). It is clear what the tool does, though it does not explicitly differentiate itself from the sibling translate_stl tool.

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 explicit guidance on when to use this tool versus alternatives such as translate_stl, nor any prerequisites or exclusions. Usage is only implied by the outcome described.

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