Skip to main content
Glama
Sign In
Kiln

Kiln

by codeofaxel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

job_history

Read-only

Retrieve the history of completed, failed, and cancelled 3D print jobs from the local durable job store, newest first. Filter by status and set a limit to review recent print outcomes.

Instructions

Get history of completed, failed, and cancelled print jobs.

        Args:
            limit: Maximum number of jobs to return (default 20, max 100).
            status: Optional filter by status -- "completed", "failed", or
                "cancelled".  Omit to show all finished jobs.

        Returns recent job records from newest to oldest, read from
        the durable job store on THIS machine (``~/.kiln/queue.db``)
        — a server restart does not shorten it.  The response
        declares its own SCOPE: ``scope.local.total_records`` gives
        the store's full matching count when ``limit`` truncated the
        page, other machines running Kiln keep their own histories,
        and the response marks itself ``incomplete`` if the durable
        store could not be read.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "job_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of jobs to return (default 20, max 100). Default: 20.
statusNoOptional filter by status -- "completed", "failed", or "cancelled". Omit to show all finished jobs.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.5.1
    • changedInput schema / properties / limit / description
      Previous value: -"Default: 20."New value: +"Maximum number of jobs to return (default 20, max 100). Default: 20."
    • addedInput schema / properties / status / description
      Added value: +"Optional filter by status -- \"completed\", \"failed\", or \"cancelled\".  Omit to show all finished jobs."
  2. Changed3 schema fields changedv1.5.0
    • removedInput schema / properties / limit / default
      Removed value: -20
    • addedInput schema / properties / limit / description
      Added value: +"Default: 20."
    • removedInput schema / properties / status / default
      Removed value: -null
  3. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Goes well past the annotations by disclosing the backing store (~/.kiln/queue.db), that history survives a server restart, that records are ordered newest to oldest, and that the response self-describes scope and an 'incomplete' flag when the store is unreadable. The one gap is that 'other machines running Kiln keep their own histories' hints at a multi-machine story without saying what this tool does about it.

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?

Front-loaded with purpose, then parameters, then return semantics, which is the right order for an agent. There is mild redundancy in the 'Args:' block duplicating schema descriptions, but no sentence is wasted and the scope warning is placed where it will be read.

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

Completeness5/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 still explains the return payload: recency ordering, scope.local.total_records for the untruncated count, and the incomplete marker. For a two-parameter read-only listing tool, an agent has everything it needs to call it and interpret the result.

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 section restates the limit and status docs nearly verbatim, so it adds essentially no meaning beyond the schema. Baseline 3 is appropriate when the schema already carries the parameter semantics.

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 history of completed, failed, and cancelled print jobs', and enumerates the three statuses it covers. It does not, however, distinguish itself from adjacent siblings such as print_history, failure_history, or list_manual_history, leaving an agent to infer which history tool it wants.

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?

The status parameter is framed as an optional narrowing filter and 'Omit to show all finished jobs' clarifies the default view, which implies when the tool is appropriate. What is missing is any explicit routing guidance against siblings like print_history or queue_summary, so the agent gets context but no exclusions.

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