Skip to main content
Glama

Get print job costs

get_print_job_costs
Read-only

Retrieve the cost breakdown for an existing print job, including line items, shipping, fees, tax, and totals; costs appear only after Lulu processes the job files.

Instructions

Get the cost breakdown of an existing Print-Job: line items, shipping, fees, tax, totals. Lulu has no costs until it has processed the job's files, and answers 'No costs are available' before then.

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": {
      "id": "<id>"
    },
    "name": "get_print_job_costs"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesPrint-Job id.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered; the description earns credit for the non-obvious behavioral detail that costs do not exist until Lulu has processed the job's files. It even quotes the 'No costs are available' response, telling the agent how to recognize that pre-processing state rather than treating it as an error. It does not cover latency or whether the call is retryable, which keeps it below 5.

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?

Two sentences, both earning their place: the first front-loads the purpose and the return contents, the second front-loads the pre-processing caveat. No filler, no restatement of the title.

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 no output schema, the description usefully enumerates the returned fields (line items, shipping, fees, tax, totals) and explains the empty-state behavior, which is enough for correct invocation. The remaining gap is routing: it never distinguishes itself from calculate_print_job_cost, which matters given how close that sibling is in name and subject.

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 100% with a single required 'id' parameter already documented as 'Print-Job id.'. The description adds only that the id must refer to an existing job, which is a minor semantic addition rather than new format or constraint guidance. Baseline 3 applies when the schema does the heavy lifting.

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 ('Get the cost breakdown of an existing Print-Job') and enumerates what the breakdown contains: line items, shipping, fees, tax, totals. The word 'existing' hints at the boundary with calculate_print_job_cost, but the sibling is never named, so the distinction still requires inference.

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 is only implied: the tool works on a job that already exists, and the reader must infer that a pre-creation estimate belongs to calculate_print_job_cost instead. There is no explicit when-to-use or when-not-to-use statement and no alternative named, though the 'existing Print-Job' phrasing gives a reasonable signal.

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