Skip to main content
Glama

Calculate print job cost

calculate_print_job_cost
Read-onlyIdempotent

Calculate total print job cost, including per-item pricing, shipping, fees and tax, before placing an order. Preview book pricing for one or more line items.

Instructions

Price one or more books, including shipping and tax, without placing an order. Returns per-line-item costs, shipping cost, fees and totals.

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": {
      "line_items": "<line_items>",
      "shipping_address": "<shipping_address>",
      "shipping_option": "<shipping_option>"
    },
    "name": "calculate_print_job_cost"
  }
}

Input Schema

NameRequiredDescriptionDefault
line_itemsYes
shipping_optionYesShipping service level, from slowest/cheapest (MAIL) to fastest (EXPRESS).
shipping_addressYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly and idempotent, and the description reinforces this with 'without placing an order' plus a disclosure of what comes back: per-line-item costs, shipping cost, fees and totals. That tells the agent the call is a safe dry-run whose payload is a cost breakdown, though it says nothing about auth requirements, rate limits, or behavior on invalid SKUs/addresses.

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 front-loaded: first what it does and its key constraint, second what it returns. Nothing is redundant or padded.

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 correctly carries the return-shape burden by naming the cost components, and it covers the safety carve-out for a read-only calculation. Remaining gaps are minor for a three-parameter pricing call: currency/precision, error handling, and how complex nested line items should be structured.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 33% and the description contributes no parameter-level meaning at all: line_items, shipping_address and shipping_option are never discussed. The only inferable hint is that 'shipping and tax' depend on an address and shipping option, which is thin compensation for the undocumented required fields.

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?

A concrete verb ('Price') plus resource ('one or more books') with the scope explicitly bounded by 'including shipping and tax' and 'without placing an order'. That last clause cleanly separates it from create_print_job, so an agent can place it without opening a sibling schema.

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?

The phrase 'without placing an order' tells the agent this is a pre-order/preview path, which is the primary when-to-use signal against create_print_job. It stops short of naming alternatives or stating exclusions (e.g. when to prefer get_shipping_options or get_print_job_costs for existing jobs), so guidance is clear but not exhaustive.

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