SimplyPrint: 3D Print Farm Management

list_files

Read-onlyIdempotent

List files and folders in the user's SimplyPrint storage. With pid set, only returns files compatible with that printer (full compatibility check). With global_search=true (default), searches recursively across all folders.

Input Schema

Name	Required	Description
`f`	No	Folder id to list (0 or omitted = root)
`limit`	No	Cap on returned files (1-500). Useful with sort_by for "5 largest files" or "10 most recent". Projects come at most 100 per page.
`start`	No
`cursor`	No	The next page of projects: pass projects_page.next_cursor from the previous answer, with the same folder, search and sort.
`search`	No	Filename substring search. Matches with or without extension — "Schleife oben 1_PLA_1h4m" and "Schleife oben 1_PLA_1h4m.3mf" both find the same file.
`compact`	No	Keep at default true. Returns minimal data tuned for AI context. Only set to false if you specifically need fields the compact view drops, and then pair with limit to keep the response small.
`sort_by`	No	Sort files by this field (folders are not affected). Default: repository order (user's saved files-page sort). Projects follow it by name or age.
`sort_dir`	No	Sort direction; default desc (newest/largest first).
`has_gcode`	No	true = only files with a parsed G-code analysis (printable); false = only non-printable files (models, etc.)
`nest_into`	No
`printer_id`	No	Only return files compatible with this printer (full compatibility check, not just model)
`files_cursor`	No
`global_search`	No	If true (default), search recursively across all folders instead of only the current one
`files_page_size`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 29, 2026
- addedInput schema / properties / files_cursor
```
Added value: +{
+  "type": "string"
+}
```
- addedInput schema / properties / files_page_size
```
Added value: +{
+  "type": "integer"
+}
```
Changed1 schema field changedOct 8, 2026
- addedInput schema / properties / start
```
Added value: +{
+  "type": "boolean"
+}
```

Changed4 schema fields changedOct 8, 2026

addedInput schema / properties / cursor

Added value: +{
+  "description": "The next page of projects: pass projects_page.next_cursor from the previous answer, with the same folder, search and sort.",
+  "type": "string"
+}

changedInput schema / properties / limit / description

Previous value: -"Cap on returned files (1-500). Useful with sort_by for \"5 largest files\" or \"10 most recent\"."New value: +"Cap on returned files (1-500). Useful with sort_by for \"5 largest files\" or \"10 most recent\". Projects come at most 100 per page."

addedInput schema / properties / nest_into
```
Added value: +{
+  "type": "string"
+}
```

changedInput schema / properties / sort_by / description

Previous value: -"Sort files by this field (folders are not affected). Default: repository order (user's saved files-page sort)."New value: +"Sort files by this field (folders are not affected). Default: repository order (user's saved files-page sort). Projects follow it by name or age."

Changed11 schema fields changedApr 25, 2026

addedInput schema / properties / compact

Added value: +{
+  "default": true,
+  "description": "Keep at default true. Returns minimal data tuned for AI context. Only set to false if you specifically need fields the compact view drops, and then pair with limit to keep the response small.",
+  "type": "boolean"
+}

addedInput schema / properties / f / description

Added value: +"Folder id to list (0 or omitted = root)"

removedInput schema / properties / f / minimum
```
Removed value: --1
```

addedInput schema / properties / global_search / description

Added value: +"If true (default), search recursively across all folders instead of only the current one"

addedInput schema / properties / has_gcode

Added value: +{
+  "description": "true = only files with a parsed G-code analysis (printable); false = only non-printable files (models, etc.)",
+  "type": "boolean"
+}

addedInput schema / properties / limit

Added value: +{
+  "description": "Cap on returned files (1-500). Useful with sort_by for \"5 largest files\" or \"10 most recent\".",
+  "type": "integer"
+}

addedInput schema / properties / printer_id / description

Added value: +"Only return files compatible with this printer (full compatibility check, not just model)"

removedInput schema / properties / printer_id / minimum
```
Removed value: -1
```

addedInput schema / properties / search / description

Added value: +"Filename substring search. Matches with or without extension — \"Schleife oben 1_PLA_1h4m\" and \"Schleife oben 1_PLA_1h4m.3mf\" both find the same file."

addedInput schema / properties / sort_by

Added value: +{
+  "description": "Sort files by this field (folders are not affected). Default: repository order (user's saved files-page sort).",
+  "enum": [
+    "name",
+    "size",
+    "created"
+  ],
+  "type": "string"
+}

addedInput schema / properties / sort_dir

Added value: +{
+  "description": "Sort direction; default desc (newest/largest first).",
+  "enum": [
+    "asc",
+    "desc"
+  ],
+  "type": "string"
+}

First observedApr 23, 2026

TDQS

A3.5/5.0

Behavior3/5

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

Annotations already establish that this is a read-only, idempotent, non-destructive operation. The description adds the default recursive search behavior and the full printer compatibility check, but does not mention pagination semantics, default compact output, or other practical listing behaviors.

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?

The description is three short sentences with no filler, and it front-loads the main purpose before qualifying behavior. Every sentence contributes directly to understanding the tool.

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 14-parameter listing tool with no output schema, the description covers only two key filters and omits pagination, sorting, search, and compact-output guidance. The schema carries much of that burden, but the description alone is not fully sufficient for correct invocation across common cases.

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 moderate at 71%, and the description only explains global_search and printer compatibility. It also refers to 'pid' while the actual parameter is printer_id, which creates avoidable naming ambiguity. The remaining parameters are left to the schema.

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

Purpose4/5

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

The description clearly states the verb and resource: listing files and folders in the user's SimplyPrint storage. It also defines important scope behavior for printer compatibility and recursive search. It stops short of explicitly differentiating from nearby siblings such as get_folder or list_print_jobs.

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?

It explains when the printer_id and global_search parameters change behavior, but it does not say when to use this tool rather than get_folder, match_file_to_printers, or other listing tools. Usage is implied rather than fully guided.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All SimplyPrint: 3D Print Farm Management tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

list_files

Input Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources