Skip to main content
Glama

Fleet view

cron_get_fleet
Read-onlyIdempotent

Check run status for each job on every node to see where it last ran and how it ended; enabled:false flags unavailable cluster peer communication.

Instructions

Run status for each job on each node. Returns enabled:false when cluster peer communication is unavailable. Use it to check where each job last ran and how it ended; use cron_get_cluster for leadership and quorum.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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, idempotentHint and destructiveHint=false, so safety is covered. The description adds genuinely useful non-obvious behavior: enabled:false is an encoding of unavailable cluster peer communication, not necessarily a disabled job — a trap an agent would otherwise misread. It stops short of describing the overall payload shape, so not a 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, zero filler: the first defines the output domain, the second gives both the use case and the sibling to prefer for the adjacent question. Front-loaded and appropriately sized for a no-argument 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?

With no parameters, strong annotations, and no output schema, the description carries the return-value burden and does explain the one surprising field value plus the last-run/last-outcome intent. The remaining fields of the per-job/per-node record are only implied, which is the one gap.

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 and the baseline is 4. The description correctly implies a whole-fleet, unfiltered read rather than a targeted query.

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 opening sentence states a specific verb and resource — a run-status matrix covering every job on every node — which is materially more precise than the tool name alone. It explicitly separates itself from cron_get_cluster (leadership/quorum). What 'status' contains is left generic, keeping 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 Guidelines4/5

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

'Use it to check where each job last ran and how it ended' gives a concrete selection scenario, and cron_get_cluster is named as the alternative for cluster-level questions. No exclusions are given against the other nearby siblings such as cron_get_status, cron_get_job, or cron_list_runs, so the routing is helpful but partial.

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