MCP 3D Printer Server

get_stl_info

Inspect STL files by path to retrieve dimensions, geometry, and other details, helping verify models before slicing or printing.

Instructions

Get detailed information about an STL file

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

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.2.9Sep 29, 2026

TDQS

C2.9/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. 'Detailed information' is undefined — it does not say whether this returns geometry stats, dimensions, triangle counts, or file metadata, nor whether it is a pure read with no side effects. The safety/behavior profile is left entirely implicit.

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 short sentence with zero padding, front-loaded with the verb. It is efficient, though its brevity is partly the cause of the gaps elsewhere rather than true economy of expression.

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?

With one fully-documented parameter and no output schema, the description is minimally adequate, but 'detailed information' gives the agent no expectation of the return payload for a tool whose entire value is the response shape. It should at least hint at what fields come back.

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% (the single stl_path parameter is documented as 'Path to the STL file'), so the schema does the heavy lifting. The description adds no format, path-style, or validation detail beyond that, which is the baseline-3 case.

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 ('Get') and resource ('STL file') with the qualifier 'detailed information', so the agent knows this is a metadata/inspection read. However, it does not distinguish itself from neighbors like generate_stl_visualization or slice_stl, which also consume an STL file.

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 statement of when to use this versus the many other STL-related siblings, nor any prerequisites (e.g., that the file must exist on the server). The agent must infer usage from the name alone.

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