Skip to main content
Glama
Sign In
Kiln

Kiln

by codeofaxel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

fleet_job_status

Read-only

Redirects fleet job status checks to split_plan_status for a fleet-wide run or job_status for one queued print; this retired name returns no status itself.

Instructions

Retired with fleet_submit_job: a run across the fleet is followed with split_plan_status, and one queued print with job_status.

        This name reads nothing any more: it only points there.
        :param job_id: Ignored: this name reads nothing.  Use
            ``split_plan_status`` or ``job_status``.

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": {
      "job_id": "<job_id>"
    },
    "name": "fleet_job_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
job_idYesIgnored: this name reads nothing. Use ``split_plan_status`` or ``job_status``.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.5.1
    • addedInput schema / properties / job_id / description
      Added value: +"Ignored: this name reads nothing.  Use ``split_plan_status`` or ``job_status``."
  2. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description is consistent with them ('this name reads nothing'). It adds the genuinely useful behavior detail that invocation is a no-op, though it does not say whether a call errors out or returns an empty/pointer result.

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?

Short and front-loaded with the retirement notice, but it carries RST artifacts (double backticks, a ':param' block pasted into prose) and repeats the same 'reads nothing' point twice, which reads as raw docstring rather than polished guidance.

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?

For a one-parameter retired stub with no output schema, the description gives everything an agent needs: do not call it, use split_plan_status for fleet runs or job_status for queued prints. Only the exact return/error behavior on invocation is left unspecified, which is minor here.

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 single job_id parameter is already documented in the schema as 'Ignored'. The description's ':param job_id' note merely restates that, adding no new meaning beyond the structured field.

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 opens with 'Retired' and states that the name 'reads nothing any more', which is the essential fact about this tool. It is not a verb+resource description of functionality, but for a deprecated stub the purpose (a dead pointer) is stated unambiguously.

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

Usage Guidelines5/5

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

It explicitly routes the agent to the replacement for each case: 'a run across the fleet is followed with split_plan_status, and one queued print with job_status', repeated in the param note. An agent knows exactly which sibling to call instead and never needs to invoke this one.

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