Slicewise

Overview Schema Source Related Servers Discussions Admin

Inspect model geometry

bambu_inspect_model

Read-onlyIdempotent

Parses STL, 3MF, or OBJ files to report triangle count, bounding box, volume, surface area, closed-mesh status, and part details, helping verify model geometry and printability.

Instructions

Parses an STL (binary or ASCII), 3MF or OBJ and reports triangle count, bounding box, volume, surface area, and whether the mesh is closed. The format is detected from the file content, not the extension. For 3MF and OBJ it also reports the part count and part list (3MF coordinates have the placement transform applied; OBJ is split into parts by o / g, and Tinkercad's colour export is OBJ). Reads only files inside the allowed directories. No side effects.

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": {
      "modelPath": "<modelPath>"
    },
    "name": "bambu_inspect_model"
  }
}

Input Schema

Name	Required	Description	Default
`modelPath`	Yes

Output Schema

Name	Required	Description
`parts`	No
`closed`	Yes
`format`	No	The format actually detected, based on the content rather than the file extension.
`openEdges`	Yes
`partCount`	No
`volumeMm3`	Yes
`boundingBox`	Yes
`triangleCount`	Yes
`surfaceAreaMm2`	Yes
`degenerateTriangles`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 7, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered; the description adds real value beyond that with format detection from content rather than extension, the 3MF placement-transform behaviour, OBJ splitting by o/g, and the allowed-directory restriction. 'No side effects' largely restates the annotations, but the format-handling caveats are the kind of behaviour an agent could not infer from structured fields.

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?

Front-loaded with the verb and the output list, then progressively narrower caveats about formats and path scope. Dense but each sentence carries information; only 'No side effects' is redundant with the annotations.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-parameter read-only inspection tool with an output schema, this covers everything an agent needs: accepted formats, how format is detected, what the numbers mean, the part-list nuance for 3MF/OBJ, and the filesystem restriction. Return-value detail is a bonus rather than a gap since an output schema exists.

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?

There is a single undocumented parameter at 0% schema coverage, so the description must carry the load; it does so by constraining the path to allowed directories and by clarifying that the extension is irrelevant because the format is sniffed from content. It still never states whether modelPath should be absolute or relative, which is the one remaining ambiguity.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (parses) and resource (STL/3MF/OBJ model files) and enumerates the exact outputs: triangle count, bounding box, volume, surface area, closedness. An agent can distinguish this from bambu_inspect_project (project vs. model) and from bambu_measure_clearance without opening any schema.

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 description of what it reports, but there is no explicit when-to-use or when-not-to-use guidance, and no routing to the closely named sibling bambu_inspect_project or to bambu_compose_model. The only hard constraint given is that it reads files inside allowed directories, which is a precondition rather than a selection rule.

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

Deploy Server