Skip to main content
Glama

My open jobs

list_open_jobs
Read-onlyIdempotent

Print jobs assigned to your shop that are not shipped yet, oldest first, with status, quantity and deadline. No buyer details. Accept and ship jobs on Printlooper. Needs a connected Printlooper account.

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

Input Schema

NameRequiredDescriptionDefault
limitNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds real value beyond that: the sort order (oldest first), the specific fields returned (status, quantity, deadline), the privacy constraint (no buyer details), and an auth prerequisite. It does not discuss pagination or truncation behavior at the limit, which is the main remaining gap.

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?

Four short sentences, front-loaded with the scope and ordering, followed by returned fields, privacy note and prerequisite. Little waste, though 'Accept and ship jobs on Printlooper' reads as a call-to-action rather than a specification of this tool and is the least load-bearing sentence.

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?

For a simple read-only list tool with no output schema and one optional parameter, the description covers what is listed, in what order, with what exclusions, and what auth is needed. The only meaningful omission is behavior when the result set exceeds the limit (pagination or truncation), which an agent would want to know.

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?

There is a single parameter, limit, with 0% description coverage, but the schema itself carries type, default (30), minimum (1) and maximum (100), so much of the meaning is already structured. The description adds nothing about the limit parameter or what happens when more jobs exist than the limit. Baseline 3 is appropriate given the schema does most of the work.

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 gives a specific verb and resource with scope: print jobs assigned to your shop that are not yet shipped, returned oldest first with status, quantity and deadline. The 'No buyer details' clause further distinguishes it from order-oriented siblings such as list_my_orders. It stops short of naming an alternative tool explicitly, so it is clear but not fully differentiated.

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?

Usage context is implied by 'Print jobs assigned to your shop that are not shipped yet' and a prerequisite is stated ('Needs a connected Printlooper account'), which is useful. However, there is no explicit when-to-use versus when-not guidance, and no pointer to sibling tools for related queries such as buyer-side orders or shop capacity. The agent must infer the boundaries.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources