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

bambu-sentinel-mcp

by selcukgk29
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

set_speed

To change print speed on a Bambu Lab printer, set the profile to silent, standard, sport, or ludicrous.

Instructions

Print speed profile: 1 silent, 2 standard, 3 sport, 4 ludicrous.

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

Input Schema

NameRequiredDescriptionDefault
levelYes
printer_idNoPrinter id; may be omitted when only one printer is configured

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior2/5

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

No annotations exist, so the description carries the full behavioral burden, yet it only labels the levels. It does not disclose whether the change affects a currently running print, whether it is persistent, or any side effects of switching profiles during a job.

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

Conciseness5/5

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

A single front-loaded sentence with the resource first and the value mapping immediately after; every word earns its place with zero waste.

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

Completeness3/5

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

For a simple two-parameter setter with no output schema, the value mapping makes it largely callable. However, with no annotations and no behavioral notes, an agent still lacks context on the effect on running prints and persistence, leaving a real 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 only 50%, but the description compensates strongly by enumerating all four meanings of the required 'level' parameter (silent/standard/sport/ludicrous), which the schema itself does not document. The optional printer_id is covered by the schema. The description adds genuine value beyond the schema.

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?

The description gives a specific verb+resource ('Print speed profile') and enumerates what each level value means, so the agent knows exactly what the tool sets. It does not explicitly differentiate from siblings like set_temperature or set_light, but the target resource is unambiguous.

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

Usage Guidelines2/5

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

There is no guidance on when to use this tool versus alternatives, nor any prerequisite context (e.g., whether it applies to an active print or persists across jobs). The agent is left to infer all usage conditions.

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