Skip to main content
Glama
JohanRouyer

Bambu Studio Advisor

by JohanRouyer
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Material guide

material_guide
Read-onlyIdempotent

Get printing advice for a material on the default printer, including filament preset, build plate, temperatures, enclosure, AMS, nozzle, and drying notes to choose the correct slicing preset.

Instructions

Give printing advice for a material on the default printer: the filament preset to use, suitable build plates and temperatures, enclosure (lid/door), AMS compatibility, nozzle and drying notes. Read-only. Use it to pick the filament preset passed to slicing tools; use list_presets to search for a specific brand.

Input Schema

NameRequiredDescriptionDefault
filamentNoExact filament preset to describe instead of the material's default one.
materialNoMaterial name: "PLA", "PLA Matte", "PETG", "ABS", "ASA", "PC", "TPU", "PA-CF"... Omit to list the materials.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.0.1
    • addedInput schema / properties / filament / description
      Added value: +"Exact filament preset to describe instead of the material's default one."
    • addedInput schema / properties / material / description
      Added value: +"Material name: \"PLA\", \"PLA Matte\", \"PETG\", \"ABS\", \"ASA\", \"PC\", \"TPU\", \"PA-CF\"... Omit to list the materials."
  2. First observedv1.0.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare read-only/idempotent/non-destructive, and the description's "Read-only" merely mirrors that. It does add real context beyond the annotations: the advice is scoped to the default printer, and it discloses the shape of the returned guidance (plates, temps, enclosure, AMS, drying), which matters since there is no output schema.

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-loads purpose in the first clause, then the returned-content list, then the usage routing. Dense and mostly waste-free, though the enumeration of advice categories is slightly list-heavy for a two-parameter tool.

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?

With no output schema, the description carries the return-value burden and does so by naming every category of advice returned. It also flags the default-printer scope, which conditions the results. Nothing needed to invoke it correctly 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?

Schema coverage is 100%, so both parameters are already documented in detail, including the "Omit to list the materials" behavior. The description adds the downstream use of the filament parameter (it is the preset passed to slicing tools), but no syntax or format guidance beyond the schema. Baseline 3 applies.

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 ("Give printing advice for a material") and enumerates exactly what the advice covers: filament preset, build plates, temperatures, enclosure, AMS, nozzle, drying. It is clearly distinguishable from siblings like list_presets or get_preset, which the description names.

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

Usage Guidelines5/5

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

Explicitly gives when-to-use ("pick the filament preset passed to slicing tools") and routes the alternative case to list_presets for brand searches. The choice between this tool and its closest sibling is fully resolved in the description.

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