Skip to main content
Glama
Sign In
orcaslicer-mcp

orcaslicer-mcp

by MaxEllis
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Compare settings

compare_settings
Read-only

Slice once per value of a single setting to get raw results for a quick sweep, then restore the original value automatically.

Instructions

Slice once per value of a single setting and return the raw numbers, putting the value back after; compare_slices adds deltas and a verdict.

The original value is put back even on error.

Use it for a quick sweep of a single key. To compare named combinations of settings with ready-to-relay deltas and a verdict, use compare_slices instead. Like compare_slices it adds one line to OrcaSlicer's MCP panel, not one per trial.

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": {
      "key": "<key>",
      "values": "<values>"
    },
    "name": "compare_settings"
  }
}

Input Schema

NameRequiredDescriptionDefault
keyYes
extraNo
valuesYes

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?

Discloses important side-effect behavior the annotations do not: the setting value is written and restored, restoration happens even on error, and the run adds one line to OrcaSlicer's MCP panel rather than one per trial. It does note that readOnlyHint=true is technically in tension with a temporary write, though the guaranteed restore makes the net effect read-only. Missing: any indication of slice duration or cost per value in the sweep.

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-loads the core mechanic, then follows with the safety guarantee, then usage and the alternative routing. Every sentence earns its place, though the opening semicolon sentence is dense and the closing panel note is a slightly detachable aside.

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 tool with no output schema, 'return the raw numbers' is only a vague gesture at the return shape, leaving the agent unsure what fields or units to expect. The mutation-and-restore contract is well covered, but the unexplained 'extra' parameter keeps the definition from being fully complete for a 3-parameter tool.

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 coverage is 0%, so the description must carry parameter meaning; it conveys that 'key' is a single setting and 'values' are the values to slice once each. However, the value type/format for the 'values' array (untyped items) and the third parameter 'extra' are entirely unexplained in both schema and description.

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 precise mechanic: slices once per value of a single setting and returns raw numbers, then names the sibling (compare_slices) that adds deltas and a verdict. An agent can distinguish this from compare_slices without opening either schema.

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

Usage Guidelines5/5

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

Explicitly scopes usage: 'Use it for a quick sweep of a single key', and names the exclusion plus the alternative for named combinations of settings. Both the when and the when-not are stated.

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