Skip to main content
Glama
Sign In
Slicewise

Slicewise

by gjlmotea
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Read back the part structure of a 3MF

bambu_inspect_project
Read-onlyIdempotent

Reads objects and parts from a Bambu project 3MF, including subtypes and per-part settings, so you can verify file contents item by item and flag unrecognized subtypes.

Instructions

Reads the objects and parts from a Bambu project 3MF, including each part's subtype and per-part settings. Use it to verify that what was written is really in the file; this is the key advantage of working with files over the GUI: you can compare item by item instead of only looking at the screen. It also flags subtypes that BambuStudio does not recognise. 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": {
      "projectPath": "<projectPath>"
    },
    "name": "bambu_inspect_project"
  }
}

Input Schema

NameRequiredDescriptionDefault
projectPathYesPath to a Bambu project 3MF.

Output Schema

NameRequiredDescriptionDefault
objectsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/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 'No side effects' adds nothing. The description earns credit for disclosing that it flags subtypes BambuStudio does not recognise, which is behavior an agent cannot infer from the schema or annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The core sentence is front-loaded and precise, but the aside about 'the key advantage of working with files over the GUI' is editorializing that does not help an agent decide or call correctly. 'No side effects' duplicates the annotations and could be cut.

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 rich annotations, full parameter coverage and an output schema, the definition covers what is needed to call the tool and what to expect conceptually. Only minor gaps remain, such as whether it fails hard on a malformed or non-Bambu 3MF.

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?

There is a single parameter (projectPath) already documented at 100% schema coverage, so the schema carries the semantics. The description adds nothing about path format, relative vs absolute, or 3MF version expectations, leaving it at the baseline.

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 and resource ('Reads the objects and parts from a Bambu project 3MF') and scopes it further to per-part subtype and settings. The 'project 3MF' scope implicitly separates it from the geometry-oriented sibling bambu_inspect_model.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

'Use it to verify that what was written is really in the file' gives a concrete trigger scenario for invoking the tool. It stops short of naming when-not to use it or pointing to an alternative sibling for other inspection needs.

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