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

bambu-printer-mcp

by DMontgomery40
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

design_guidance

Read-onlyIdempotent

Read FDM design guidance by topic (fit, flexures, assembly, multicolor, after-slice, capability) to decide print design choices when tools exist but prompts are unavailable.

Instructions

Read one piece of this MCP's design guidance by name: fdm_fit (when a part meets a real object or another part); fdm_flexures (when a part must flex, grip, snap, clip, spring, or hold something by bending); fdm_assembly (when a split, joint, insert or printed thread could improve the result); fdm_multicolor (when several colours or support materials share a print); fdm_after_slice (when a candidate has been sliced, before recommending it); fdm_capability (when a bridge or overhang decides the plan and no measured capability is at hand). The same texts as the prompts of those names, for a worker that has tools but not prompts. Read-only.

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

Input Schema

NameRequiredDescriptionDefault
nameYesWhich guidance to read.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.1.93

TDQS

A4.5/5.0
Behavior4/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 'Read-only' is redundant. What the description does add is provenance: the content is the same text as the like-named prompts, intended for a tool-only worker — genuinely useful behavioral context that is not in any structured field.

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?

The verb and resource are front-loaded and no sentence is filler, but the guidance enumeration is packed into one very long sentence with nested parentheticals, which is dense to parse. Splitting the six triggers into a list structure would improve scanability without adding length.

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?

For a one-parameter read-only lookup with full schema coverage and annotations, the definition covers the key unknowns: what each name means and why the tool exists alongside the prompts. It does not hint at output length or shape, which matters little since the content is prose guidance, but it is the one remaining gap.

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?

Schema coverage is 100% and the enum is self-describing, so the baseline is 3. The description goes further by attaching a design situation to each enum value, which tells the agent far more about which name to pick than the terse schema line 'Which guidance to read.'

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?

Opens with a specific verb and resource ('Read one piece of this MCP's design guidance by name') and then enumerates every valid name with its subject matter. An agent knows exactly what it gets and can distinguish this from any generation or checking tool in the sibling list.

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?

Each of the six enum values carries an explicit trigger condition ('when a part meets a real object', 'when a candidate has been sliced, before recommending it'). This is effectively a decision table that tells the agent which guidance to fetch and in what situation, with no inference required.

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