Skip to main content
Glama
Sign In
orcaslicer-mcp

orcaslicer-mcp

by MaxEllis
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Get preset config

get_preset_config
Read-only

Reads all settings from a named print, filament, or printer preset without selecting it, so you can inspect preset values while leaving the live configuration unchanged.

Instructions

Read every setting of a named preset without selecting it; get_config reads the live settings.

type = print|filament|printer.

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

Input Schema

NameRequiredDescriptionDefault
nameYes
typeYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.8

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, but the description adds meaningful context beyond them: the read does NOT activate/select the preset, which is the key side-effect concern when inspecting presets. It says nothing about behavior for a nonexistent preset name or the shape of the returned settings.

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?

Two tight clauses with the key contrast front-loaded; nothing is redundant. The dangling 'type = print|filament|printer.' line is slightly unpolished in placement but earns its place as parameter documentation.

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 two-required-parameter read tool with no output schema and 0% schema description coverage, the definition documents the type values but leaves the name parameter entirely opaque, which is the main gap an agent would hit when calling it.

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 0%, and the description does supply the only enum-like information available for 'type' (print|filament|printer), which is genuinely valuable. However, the 'name' parameter remains completely unexplained — where preset names come from or how they are matched — so it only partially compensates for the coverage gap.

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?

The description states a specific verb and resource ('Read every setting of a named preset') and explicitly contrasts scope with the sibling get_config ('get_config reads the live settings'), so an agent can distinguish the two without opening schemas.

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?

It gives a clear selection rule: use this to inspect a stored preset, use get_config for live settings. It stops short of naming other useful routes (e.g. how to discover preset names, or what to do if the preset is missing), so no explicit exclusions beyond the one sibling.

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