Skip to main content
Glama
Sign In
Kiln

Kiln

by codeofaxel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

fleet_analytics

Read-only

Retrieve historical analytics for every registered 3D printer, including success rates, utilization, job throughput, print duration, and fleet-wide aggregates to monitor performance.

Instructions

Get fleet historical analytics: per-printer success rates, utilization, job throughput.

        For live printer status (current state/temps), use ``fleet_status``.
        Returns statistics for every registered printer including total prints,
        success rate, average print duration, and total print hours.  Also
        includes fleet-wide aggregate metrics.

        Requires Business license.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds genuinely new behavioral context: a Business license prerequisite and a summary of what the payload contains (per-printer stats plus fleet-wide aggregates). It stops short of noting cost, latency, or coverage window (all-time vs. bounded range).

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 the sibling routing hint, then return contents, then the license gate — a sensible order. The one inefficiency is that "success rates" and "job throughput" are restated as "success rate... total print hours" in the third sentence, a mild duplication that costs a few words.

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 parameterless, read-only aggregate with no output schema, the description carries the needed load: it says what comes back, at what granularity, and that it covers every registered printer. The remaining gap is scope of time — nothing says whether the analytics cover all history or a default window — which matters for interpreting the numbers.

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 are no parameter semantics for the description to explain; the baseline applies. The description correctly implies the call is unfiltered (every registered printer), which is the only semantic an agent could get wrong here.

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?

"Get fleet historical analytics: per-printer success rates, utilization, job throughput" gives a specific verb, resource, and enumerated metrics, and the second sentence explicitly separates it from the live-state sibling fleet_status. An agent can pick between the two without opening either 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 names one alternative (fleet_status) and the condition that selects it (live current state/temps vs. historical), which is real routing guidance. It doesn't address the many other analytics/statistics siblings such as fleet_utilization, printer_stats, printer_usage_summary, or usage_summary, so the disambiguation is partial rather than exhaustive.

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