Skip to main content
Glama
Sign In
OrcaSlicer-mcp

OrcaSlicer-mcp

by BeMuCa
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

printer_files

Lists G-code files stored on an Elegoo printer, enabling MCP clients to see available print jobs before slicing or starting a print.

Instructions

G-code files stored on the Elegoo printer.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.8/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full burden, and it discloses almost nothing. It does not state that the operation is a read, whether files are listed or fetched, whether results are paginated or ordered, or whether the printer must be reachable.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The single sentence is efficient with no wasted wording, but it is under-specified rather than concise: a verb-led phrasing such as 'List G-code files on the printer' would have cost the same length and removed the ambiguity.

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?

An output schema exists, so return values need not be explained, and a zero-parameter read tool is low complexity. Even so, the absence of a verb and of any usage or behavioral context leaves the agent inferring what the call actually does.

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, so there is no parameter meaning for the description to add; the baseline of 4 applies. The empty schema leaves nothing undocumented.

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?

The description names a specific resource (G-code files) and scope (on the Elegoo printer), which is more than a tautology. However, it is a bare noun phrase with no verb, so an agent cannot tell whether the tool lists files, returns their contents, or reports metadata, and it does not distinguish itself from siblings like upload_to_printer or start_print.

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

Usage Guidelines2/5

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

There is no when-to-use guidance at all. It does not say to call this before upload_to_printer or start_print, nor does it state any preconditions (e.g., printer must be online).

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