Skip to main content
Glama
Sign In

SimplyPrint: 3D Print Farm Management

by io.simplyprint
OverviewDiscussionsAdmin

list_maintenance_jobs

Read-onlyIdempotent

List maintenance jobs across the account with filters, paging and sorting — the tool for "what maintenance is outstanding, and on which printer". Each job carries its printer, priority, scheduled date, task progress, assignees and linked problems. Returns 10 per page by default; raise page_size (max 100) or advance page. IMPORTANT: a returned job status may read "overdue", but that value is DERIVED (a scheduled job whose scheduled_date has passed) and is NOT accepted by the status filter — ask for status "scheduled" and read each job's returned status, or use the dashboard's overdue count.

Input Schema

NameRequiredDescriptionDefault
pageNoPage number (1-based).
datedNoOnly jobs with a scheduled_date. With sort_id scheduled_date and sort_dir asc this lists what is due next; without it, undated jobs sort first.
searchNoSubstring match over job title, description and printer name.
statusNoFilter by stored job status. "overdue" is not a stored status and is rejected here — it is derived from scheduled_date at read time.
sort_idNoSort field; default created_at.
sort_dirNoSort direction; default desc.
page_sizeNoJobs per page, 1-100. Defaults to 10 over MCP; job records are large.
printer_idNoOnly jobs for this printer. Takes precedence over printer_ids.
printer_idsNoOnly jobs for these printers, as a comma-separated list of ids ("4,9,12"). Ignored when printer_id is set.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / dated
      Added value: +{
+  "description": "Only jobs with a scheduled_date. With sort_id scheduled_date and sort_dir asc this lists what is due next; without it, undated jobs sort first.",
+  "type": "boolean"
+}
  2. Added

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the readOnly/non-destructive annotations, the description discloses important behavior: default page size, maximum page size, the fact that job records are large, and critically that 'overdue' is derived at read time rather than a filterable stored status. This is exactly the kind of non-obvious behavior an agent needs before calling the tool.

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 front-loaded with the tool's purpose and scope, then moves to paging behavior, then the critical status caveat. It is compact for nine parameters and no sentence feels wasted.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given nine optional parameters, rich annotations, no output schema, and sibling tools for detail/dashboard views, the description is complete enough to call correctly. It names returned fields, paging defaults, page-size limits, and the main filtering gotcha.

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?

With 100% schema description coverage, the schema already documents all parameters well. The description still adds value by explaining the practical paging behavior and reinforcing the derived 'overdue' status caveat, though most parameter-specific details remain in the schema rather than the 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?

The description states a specific verb and resource: 'List maintenance jobs across the account with filters, paging and sorting.' It also distinguishes the tool's job-to-be-done with the phrase 'what maintenance is outstanding, and on which printer,' which separates it from detail-oriented siblings like get_maintenance_job or dashboard tools.

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?

Usage context is clear: use this for outstanding maintenance and printer association, with guidance to raise page_size or advance page. The status caveat explicitly tells the agent not to filter by 'overdue' and to use 'scheduled' instead, but it does not explicitly name an alternative sibling such as get_maintenance_dashboard beyond a passing reference.

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 toolsInspect
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.

Resources