Skip to main content
Glama
Sign In
bambu-printer-mcp

bambu-printer-mcp

by DMontgomery40
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

get_stl_info

Read-onlyIdempotent

Retrieve detailed STL file information, including bounding box, face count, and dimensions, to analyze 3D models before slicing or printing.

Instructions

Get detailed information about an STL file (bounding box, face count, dimensions)

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

NameRequiredDescriptionDefault
stl_pathYesPath to the STL file to analyze

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.1

TDQS

A3.5/5.0
Behavior3/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 fully covered externally. The description's only added behavior is the list of returned metrics, and it says nothing about failure behavior for a missing or malformed STL path or about cost/latency for large files.

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 front-loaded sentence with the resource up front and the return fields in a compact parenthetical. Nothing is redundant; it is short almost to a fault, but it is well structured.

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 must convey what comes back, and it does name the key metrics (bounding box, face count, dimensions), which is adequate for a one-parameter inspection tool. It stops short of explaining returned units or error conditions, but nothing an agent needs to invoke it is missing.

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 with 100% schema description coverage, so the schema already explains stl_path. The description adds no format, path-root, or relative-vs-absolute guidance beyond what the schema provides; baseline 3 applies.

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 ('information about an STL file') and enumerates what is returned (bounding box, face count, dimensions). It is clearly distinct from mutating siblings like scale_stl or slice_stl, though it never names an alternative 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 only implied: an agent can infer this is the read-only inspection step before scale_stl, rotate_stl, or slice_stl, but the description never says when to call it or when another tool is a better choice. No prerequisites or exclusions are given.

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