Skip to main content
Glama
Sign In
Kiln

Kiln

by codeofaxel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

recent_events

Read-only

Retrieve recent Kiln event bus activity to monitor job lifecycle, printer state changes, and safety warnings, with optional type-prefix filtering and a result limit.

Instructions

Get recent events from the Kiln event bus.

Args:
    limit: Maximum number of events to return (default 20, max 100).
    type: Filter by event type prefix (e.g. ``"print"`` matches
        ``print.started``, ``print.completed``; ``"job"`` matches
        ``job.submitted``, ``job.completed``).  Omit for all events.

Returns events covering job lifecycle, printer state changes,
safety warnings, and more.

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

Input Schema

NameRequiredDescriptionDefault
typeNoFilter by event type prefix (e.g. ``"print"`` matches ``print.started``, ``print.completed``; ``"job"`` matches ``job.submitted``, ``job.completed``). Omit for all events.
limitNoMaximum number of events to return (default 20, max 100). Default: 20.

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 events to return (default 20, max 100). Default: 20."
    • addedInput schema / properties / type / description
      Added value: +"Filter by event type prefix (e.g. ``\"print\"`` matches ``print.started``, ``print.completed``; ``\"job\"`` matches ``job.submitted``, ``job.completed``).  Omit for all events."
  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 / type / default
      Removed value: -null
  3. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare this a safe, non-destructive, closed-world read, so the safety profile is covered. The description adds useful context beyond that: the 20-default/100-max cap and the fact that results span job lifecycle, printer state changes, and safety warnings. It omits ordering (is "recent" newest-first?), whether results are truncated when the limit is hit, and how events are structured.

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 the core purpose in one sentence, followed by a compact returns summary. The Args block is redundant at 100% schema coverage, but the overall length stays proportionate to a two-parameter read tool.

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 simple, optional-parameter read tool with no output schema, the description covers what the tool does, what the filter matches, and the categories of events returned. Only the result ordering and the shape of an individual event remain unspecified, which is a minor gap.

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%, so the Args block largely restates the schema's own parameter descriptions. The prefix-matching examples ("print" matching print.started/print.completed) are genuinely helpful semantics, but they are already present verbatim in the schema, so no meaning is added beyond the structured data.

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 recent events from the Kiln event bus") and adds the domain covered (job lifecycle, printer state changes, safety warnings), so an agent can tell it is an event-feed reader rather than a job or printer status tool. It does not name a sibling alternative to differentiate against, which keeps it short of a 5.

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?

No when-to-use or when-not-to-use guidance. With siblings like job_history, printer_stats, and monitor_print available, the description never says whether this is the right tool for polling status versus auditing past activity, so the agent must infer the choice from the name alone.

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