Skip to main content
Glama
Sign In
SlicerBridge

SlicerBridge

by UnicornGraveyard
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

list_printers

Read-onlyIdempotent

Retrieve every printer SlicerBridge supports, including key, name, engine, slicer, colors, and sets, so you can identify valid printer keys for filtering or conversion.

Instructions

Every printer SlicerBridge writes for: its key, name, engine, slicer, the colors it holds, and the sets it's in.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_printers"
  }
}

Input Schema

NameRequiredDescriptionDefault
printersNoWhich printers: 'all', a set (popular), a vendor (bambu, creality, elegoo, anycubic, flashforge, qidi, wondermaker, prusa, snapmaker), or printer keys from list_printers, comma-separated.all

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety and idempotency profile is fully covered structurally. The description adds no behavioral context beyond that — no cost, no pagination, no staleness/caching notes — and its field enumeration largely duplicates the 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?

One tight sentence with zero filler, and the field list is delivered compactly. It is grammatically a fragment and spends its whole budget on return shape rather than on the filtering behavior an agent actually needs, but there is no verbosity to penalize.

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?

An output schema exists, so describing return fields is redundant effort, while the one thing the description should have covered — that results can be scoped by set/vendor/key — is omitted. For a single-parameter read tool this is still callable, but the description's emphasis is misallocated.

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 description coverage is 100% and the single 'printers' parameter is documented in detail, including the enumerated vendor values and the cross-reference back to list_printers keys. The description contributes nothing to parameter understanding and in fact mildly works against it by implying every printer is always returned. 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?

The description makes clear this enumerates the printer catalog SlicerBridge knows about, and lists the fields each entry carries (key, name, engine, slicer, colors, sets). The action verb is implicit ("Every printer..." rather than "List"), but the resource is unambiguous and no sibling (convert_model, inspect_model, verify_files, brand_check, doctor) could be confused with it.

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 statement of when to call this versus siblings, no prerequisite, and no exclusion. Worse, the description's framing ("Every printer") never acknowledges that the single parameter lets the agent scope the result to a set, vendor, or specific keys — the schema says so, but the description implies an unfiltered dump.

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