Skip to main content
Glama
Sign In
orcaslicer-mcp

orcaslicer-mcp

by MaxEllis
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

List presets

list_presets
Read-only

List your own and currently selected print, filament, and printer presets, with options to include system presets or filter by preset type.

Instructions

List the print, filament and printer presets: the user's own and the selected ones, or all with include_system.

Each with system/selected/visible flags.

F12: by default returns only USER presets plus whatever is currently SELECTED - the built-in system presets are ~400 entries of noise. Pass include_system=True for the full list, and/or type='print'|'filament'|'printer' to restrict to one category. hidden_system reports how many system presets were filtered out.

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_presets"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeNo
include_systemNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.8

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already establish readOnlyHint=true, so the safety profile is covered. The description adds genuinely non-obvious behavior beyond that: the default deliberately filters ~400 built-in presets as 'noise' and the response includes a hidden_system count reporting how many were dropped — important for interpreting an apparently short result. It does not describe the flags' semantics in detail (system/selected/visible are named but not explained).

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-loaded with the core purpose and scope, then the parameter rules — a sensible order with little waste. The 'F12:' prefix is unexplained internal jargon that adds no meaning for an agent and slightly undercuts the otherwise clean structure.

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 two-parameter read-only list tool with no output schema, the description covers purpose, defaults, filtering escape hatches, and the filtering counter. Remaining gaps — no mention of result ordering, size limits, or what the system/selected/visible flags mean — are minor but real.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% and the 'type' property is a bare string with no enum, so the description carries the full burden. It does: it supplies the three legal values ('print'|'filament'|'printer'), explains include_system's effect on result size, and clarifies the default filtering that neither parameter alone would reveal.

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?

Opens with a specific verb+resource ('List the print, filament and printer presets') and immediately defines the returned scope: the user's own plus the selected ones. It does not distinguish itself from presets-related siblings such as get_preset_config, edit_preset or delete_preset, so an agent can tell what it does but not precisely where it sits among alternatives.

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

Usage Guidelines4/5

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

Gives clear, actionable usage rules for the two parameters: default is user+selected, pass include_system=True for the full list, and/or type='print'|'filament'|'printer' to restrict. What's missing is routing guidance versus sibling tools (e.g., when to list presets versus read a single preset's config).

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