Skip to main content
Glama
Sign In
Kiln

Kiln

by codeofaxel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

print_service_quote

Destructive

Confirm a print service order and begin processing by providing the order ID and selecting local, fulfillment, or the recommended quote option.

Instructions

Confirm a print service order and start processing.

        Args:
            order_id: The order ID from ``create_print_service_order``.
            option: ``"local"`` or ``"fulfillment"``.  ``"recommended"``
                (the default) confirms whichever of the two the quote's
                ``recommended`` field named.

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

Input Schema

NameRequiredDescriptionDefault
optionNo``"local"`` or ``"fulfillment"``. ``"recommended"`` (the default) confirms whichever of the two the quote's ``recommended`` field named. Default: "recommended".
order_idYesThe order ID from ``create_print_service_order``.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.5.1
    • changedInput schema / properties / option / description
      Previous value: -"Default: \"recommended\"."New value: +"``\"local\"`` or ``\"fulfillment\"``.  ``\"recommended\"`` (the default) confirms whichever of the two the quote's ``recommended`` field named. Default: \"recommended\"."
    • addedInput schema / properties / order_id / description
      Added value: +"The order ID from ``create_print_service_order``."
  2. Changed2 schema fields changedv1.5.0
    • removedInput schema / properties / option / default
      Removed value: -"recommended"
    • addedInput schema / properties / option / description
      Added value: +"Default: \"recommended\"."
  3. 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 readOnlyHint=false and destructiveHint=true, so the safety profile is covered. The description adds that confirmation kicks off processing, which is useful state-change context, but it does not say whether the action is reversible, whether it commits cost, or whether a second confirmation is possible.

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?

The lead sentence is front-loaded and does the core work. The Args block largely restates the schema, which is mild redundancy rather than noise, and the nested quoting in the option explanation is slightly cluttered.

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 two-parameter mutation with no output schema, an agent still lacks the outcome: no description of what is returned (confirmation, job or quote ID) or how to follow progress. Annotations carry the destructive flag, but the description should close the loop on post-confirmation tracking.

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 description coverage is 100% and the parameter text in the description is essentially a duplicate of the schema. It does convey that "recommended" resolves to whichever option the quote flagged, which is helpful semantics, but that same explanation is already present in the schema field description, so no net value is added.

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 ("Confirm a print service order") plus the effect ("start processing"), which clearly separates it from siblings like cancel_print_service_order or print_service_status. It stops short of explicitly naming the sibling it complements, but the reference to the order ID from create_print_service_order implies the create-then-confirm sequence.

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 parameter docs reveal that an order must first exist from create_print_service_order. There is no explicit when-to-use versus when-not-to-use guidance, no mention of what happens if the order was already confirmed, and no pointer to print_service_status for tracking after confirmation.

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