Skip to main content
Glama
Sign In
Kiln

Kiln

by codeofaxel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

cancel_print_service_order

Destructive

Cancel a print service order that has not started printing, preventing queued jobs from proceeding.

Instructions

Cancel a print service order.

        Only orders that have not started printing can be cancelled.

        Args:
            order_id: The order ID to cancel.

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": {
      "order_id": "<order_id>"
    },
    "name": "cancel_print_service_order"
  }
}

Input Schema

NameRequiredDescriptionDefault
order_idYesThe order ID to cancel.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.5.1
    • addedInput schema / properties / order_id / description
      Added value: +"The order ID to cancel."
  2. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the mutating nature is known. The description adds the state precondition, which is useful, but says nothing about irreversibility of the cancellation, whether a refund or status change occurs, or what error an agent sees when printing has already started.

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?

Two sentences, front-loaded with the action and then the precondition; nothing is wasted. The Args block is a minor duplication of the input schema but does not hurt readability.

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

Completeness3/5

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

For a destructive single-parameter tool with no output schema, the definition covers the action and the eligibility rule but leaves the post-call state (what the order becomes, whether the action is reversible) unexplained. That gap matters more here than for a read-only tool.

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% and the description's Args block restates the schema text verbatim ('The order ID to cancel'). It adds no format, source, or lookup guidance for obtaining the order_id, so the baseline 3 applies.

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 states a specific verb and resource ('Cancel a print service order'), so an agent knows exactly what the tool acts on. It does not, however, distinguish this from the many other cancellation siblings such as cancel_print, cancel_queued_job, fulfillment_cancel, or cancel_print_recovery.

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?

It gives one real precondition ('Only orders that have not started printing can be cancelled'), which helps an agent decide if the call is legal. It never says which sibling to use instead, or how this differs from cancel_print_service_order-adjacent tools like cancel_queued_job or create_print_service_order workflows.

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