Skip to main content
Glama
Sign In
Kiln

Kiln

by codeofaxel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

fleet_status_by_site

Read-only

Redirects legacy references to fleet_status(by_site=True), showing printers grouped by site with idle, busy, and needs-repair status; it reads no printer data.

Instructions

Retired: the fleet grouped by site is fleet_status(by_site=True).

        There is one fleet view.  ``fleet_status`` lists every printer;
        with ``by_site=True`` the same answer is also grouped by site,
        with each site's idle, busy and needs-repair printers.  This name
        answers nothing any more: it only points there, so an old guide
        or habit still leads somewhere.  It reads no printer.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/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; the description adds genuinely new behavioral facts — that the tool is retired, returns only a pointer, and reads no printer. That is more than the annotations convey, though it doesn't say what the pointer response actually looks like.

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 same fact is restated three times (retired, 'answers nothing any more', 'only points there'), and the backticked indented prose is awkward. The core message would survive at half the length, though it is at least front-loaded with 'Retired'.

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 no-parameter deprecated alias with no output schema, the definition supplies everything needed: deprecation status, the successor call, and the guarantee of no side effects. Only the exact return payload is unspecified, which is minor.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so there is nothing for the description to disambiguate. The mention of by_site=True belongs to the successor tool's semantics, which is a helpful pointer but outside this tool's schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The first line states precisely what this name is (retired) and what it maps to (fleet_status(by_site=True)), and the last line states its actual effect: 'It reads no printer.' An agent can distinguish this from fleet_status without opening a schema.

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

Usage Guidelines4/5

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

It explicitly names the replacement call to make instead ('the fleet grouped by site is ``fleet_status(by_site=True)``') and explains why the name still exists (old guides/habits). It stops short of an imperative 'do not call this' but the routing intent is unambiguous.

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