Skip to main content
Glama
io.github.crunchtools/systemd

io.github.crunchtools/systemd

by crunchtools

Timer List Tool

timer_list_tool
Read-only

Lists systemd timers with their next and last elapse times, showing which scheduled jobs will fire and when they last ran. Flags timers with unreadable properties via an error field.

Instructions

List systemd timers with their next and last elapse times.

A null next_elapse or last_trigger means systemd gave no renderable time: unset (the timer has not run yet), infinity (it will never fire again), or a value outside the renderable range. A timer whose properties could not be read at all carries an error field instead of the two times.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=true, so the description carries most of the burden and does so well: it explains that a null next_elapse or last_trigger encodes unset, infinity, or an out-of-range value, and that an error field appears when properties cannot be read. It does not mention failure modes such as systemd being unavailable, but the edge-case semantics it does provide are substantive.

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?

The first sentence front-loads the core purpose, and the remainder is a compact, well-scoped note on interpreting edge-case values. It is appropriately sized for a no-parameter list tool, though the null/error explanation could be tightened slightly.

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 read-only, zero-parameter listing tool with an output schema and readOnlyHint already declared, the description covers the interpretive gap that structured fields cannot: what null and error mean. The one missing element is routing guidance relative to sibling listing tools.

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 no parameters at all, which is the baseline-4 case; there is nothing for the description to disambiguate. The schema declares an empty object with additionalProperties=false, and the description correctly implies a no-argument listing call.

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 a specific verb and resource: 'List systemd timers with their next and last elapse times,' which tells an agent exactly what the tool returns. It does not explicitly name a sibling such as unit_list_tool as the alternative, so it stops short of full sibling differentiation.

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?

There is no guidance on when to use this tool versus unit_list_tool or system_status_tool, and no stated preconditions. Usage is only implied by the name and the resource mentioned, so an agent must infer the choice itself.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.