Skip to main content
Glama

get_job_status

Read-onlyIdempotent

Retrieve current 3D print job details, including state, filename, layer and file progress, durations, filament used, estimated remaining time, and slicer metadata for the running file.

Instructions

Detail on the current print job: state, filename, progress by both layer and file position, durations, filament used, estimated remaining time, and the slicer metadata for the running file.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.1

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds the data categories the tool surfaces, which is useful, but says nothing about the key edge case for a status tool: what is returned when there is no active job, or how stale/live the data is.

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?

A single front-loaded sentence that leads with the resource and then lists contents; every clause names a distinct data category with no padding. It is long-ish but dense rather than verbose.

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

Completeness4/5

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

With an output schema present, the description needn't detail return shapes, and the read-only behavior is covered by annotations. What it omits is small but real for a status tool: behavior when idle and whether output reflects a queued job versus a running one.

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 nothing for the description to disambiguate; baseline 4 applies. The schema has no properties for the description to contradict or duplicate.

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?

States a specific verb and resource ('Detail on the current print job') and enumerates the contents: state, filename, progress, durations, filament, remaining time, slicer metadata. This clearly separates it from the sibling get_printer_status, which covers the machine rather than the active job, though the description never names that sibling explicitly.

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 word 'current' implies this is for monitoring an in-progress job, but there is no explicit when-to-use versus get_printer_status, get_job_queue, or get_print_history, and no guidance on what callers should expect when nothing is printing.

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