Skip to main content
Glama
Sign In
OrcaSlicer-mcp

OrcaSlicer-mcp

by BeMuCa
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

printer_info

Retrieves Elegoo Centauri 2/Carbon 2 system information in LAN-only mode to help MCP clients verify printer status and configuration.

Instructions

Elegoo Centauri 2 / Carbon 2 system info (LAN-only mode). Needs ELEGOO_HOST and ELEGOO_TOKEN or ~/.config/elegoo_token.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full disclosure burden, and it does add real behavioral context: LAN-only mode plus the required ELEGOO_HOST/ELEGOO_TOKEN environment variables or the ~/.config/elegoo_token file. It does not state that the operation is read-only, whether it fails hard when credentials are absent, or what the response contains.

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 short sentences, front-loaded with what the tool is, followed by the authentication prerequisite. Nothing is padded, though 'system info' could be replaced with one concrete example of the data returned at no cost in length.

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 zero-argument tool with no output schema, the auth and network-mode requirements are the key omissions it successfully covers. What remains missing is the content of 'system info' and how it relates to the many sibling printer tools, which is the main source of agent confusion here.

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?

The tool takes zero parameters and the schema is fully covered, so there is nothing for the description to disambiguate. Baseline 4 applies; no parameter meaning is missing.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

It names a resource (system info) scoped to a specific printer family (Elegoo Centauri 2 / Carbon 2), so the vendor/model is clear. However, 'system info' is vague about what is actually returned, and it never distinguishes itself from siblings such as printer_status, printer_files, or slicer_info, which an agent must choose between.

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

Usage Guidelines3/5

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

The '(LAN-only mode)' qualifier and the credential prerequisites imply the conditions under which the call can succeed, which is genuinely useful. There is still no explicit statement of when to pick this over printer_status or how it differs, so the routing decision is left to inference.

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