Skip to main content
Glama
Sign In

Cloudlabels

by io.cloudlabels
OverviewDiscussionsAdmin

Get print job

get_print_job
Read-onlyIdempotent

Requires print. Read a print job from start_print_job. Pass job_id. status is queued, processing, completed, or failed. A job that is still waiting, running, or retrying stays queued or processing. failed is used when the attempts are used up, or when the PDF finished without a stored file. progress is included when the queue has it. failed includes error. completed includes download_url, a signed https link on a cloudlabels.io host that streams the PDF for 48 hours. If progress has expired but the PDF is still stored for this organization, status is completed with download_url. An unknown job_id and a job from another organization both return status not_found.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "job_id": "<job_id>"
    },
    "name": "get_print_job"
  }
}

Input Schema

NameRequiredDescriptionDefault
job_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Beyond the readOnly/idempotent annotations, the description discloses detailed status semantics, how queued/processing/failed/completed are assigned, when progress and error appear, the 48-hour signed download_url behavior, expiry handling, and the not_found case for unknown or cross-organization job IDs.

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 core action and parameter, then proceeds through status behavior and edge cases. Every sentence adds operational meaning, including status transitions, download URL lifetime, and not_found handling.

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?

Although there is no output schema, the description explains the important return fields and statuses an agent needs: progress, error, download_url, expiry behavior, and not_found. It is complete enough for correct invocation and interpretation.

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 coverage is 0%, so the description must carry parameter meaning. It says to pass job_id and ties it to start_print_job, and it explains not_found behavior for unknown or other-organization IDs, but it does not describe the expected ID format or syntax.

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: 'Read a print job from start_print_job.' It clearly distinguishes this retrieval tool from the sibling start_print_job creation tool and tells the agent exactly what entity is being read.

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?

It gives clear usage context by saying the job comes from start_print_job and that job_id must be passed. However, it does not explicitly state when not to use this tool or name alternative tools for related print-job operations.

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

All Cloudlabels 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