Skip to main content
Glama
Sign In
Kiln

Kiln

by codeofaxel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

print_service_status

Read-only

Check the status of a print service order by order ID to track its progress.

Instructions

Check the status of a print service order.

        Args:
            order_id: The order ID to check.

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_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
order_idYesThe order ID to check.

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 check."
  2. First observedv0.1.0

TDQS

C2.8/5.0
Behavior2/5

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

The annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered without the description. Beyond that the description adds nothing: no statement of what 'status' contains, whether unknown order IDs error or return empty, or any auth/quota context — and there is no output schema to fill that gap.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The core sentence is front-loaded and unambiguous, which is good. However, the trailing Args block is pure duplication of the input schema and consumes roughly half the text without adding information.

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

Completeness2/5

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

For a status-lookup tool with no output schema, the description should indicate what status values or fields come back so the agent can interpret the result. It does not, and it also omits how the order_id is obtained, leaving the agent to infer both ends of the call.

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 single parameter is fully documented in the schema. The description's Args block repeats the schema text verbatim ('The order ID to check'), adding no format, example, or provenance detail (e.g., where the ID comes from — create_print_service_order).

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 — 'Check the status of a print service order' — so an agent can tell this reads order state rather than creating or cancelling one. It offers no contrast with nearby siblings such as create_print_service_order, cancel_print_service_order, or fulfillment_order_status, so differentiation stops at the name.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use guidance, no prerequisites, and no named alternatives. Given the sibling list contains several status-like tools (fulfillment_order_status, job_status, pipeline_status), an agent gets no help choosing among them.

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