Skip to main content
Glama
Sign In
orcaslicer-mcp

orcaslicer-mcp

by MaxEllis
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Get config values

get_config
Read-only

Read current OrcaSlicer setting values, optionally limited to specific keys, merged across active print, filament, and printer presets.

Instructions

Read the current value of settings (all, or only keys); to learn what a setting means or its allowed range use describe_setting.

Values come back as text, merged across the active print, filament and printer presets.

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": "get_config"
  }
}

Input Schema

NameRequiredDescriptionDefault
keysNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.8

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, so the description doesn't need to restate safety; instead it adds genuinely new behavioral context — results are returned as text and are merged across the active print, filament and printer presets, which explains why a value may differ from what a single preset file contains. It stops short of covering unknown-key behavior or ordering.

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?

Two short sentences, front-loaded with the primary action and its modes, followed by the sibling routing and the return-format note. No filler or repetition of the title.

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 tool with no output schema, the description covers what is returned (text values) and how preset merging affects them. Minor gaps remain around error behavior for unknown keys and result ordering, but nothing essential to calling it correctly is missing.

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 description coverage is 0%, so the description must carry the meaning, and it does: omitting `keys` returns all settings, while supplying `keys` restricts output to those setting names. That resolves the only real ambiguity in a single-parameter schema, though it doesn't say how invalid keys are handled.

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?

States a specific verb and resource ('Read the current value of settings') plus the two modes (all, or only `keys`), and explicitly separates itself from describe_setting. An agent can distinguish it from describe_setting and set_config without opening any schema.

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 an explicit alternative with the selecting condition: use describe_setting when you need a setting's meaning or allowed range. It does not address scope questions such as when to prefer preset-scoped reads, but the core routing guidance is clear and unambiguous.

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