Skip to main content
Glama

Version

cron_get_version
Read-onlyIdempotent

Retrieve the server version, job-set ID, and job count to identify a daemon and compare job-set IDs across replicas to check whether their job configurations agree.

Instructions

Show the server version, job-set ID, and job count. Use it to identify the daemon, or to compare job-set IDs across replicas, which match when the replicas' jobs agree on the configuration fields the ID covers, even if secret values or host-specific settings differ; use cron_get_cluster for the replicas' roles.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the description doesn't need to. It adds real behavioral context instead: what the job-set ID means, that it matches across replicas when configuration fields agree, and that it ignores secret values and host-specific settings.

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 what it returns, then usage and the sibling pointer. The job-set ID sentence runs long with a nested clause, but every clause carries meaning an agent would otherwise have to infer.

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 output schema, the description must say what comes back, and it does (version, job-set ID, job count). It also flags the main subtlety, which is job-set ID equality semantics across replicas, so the agent almost never needs anything more.

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 the baseline is 4. There is nothing for the description to compensate for.

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?

States a specific verb and resource ('Show the server version, job-set ID, and job count') and even enumerates the fields returned. That makes it immediately distinguishable from siblings like cron_get_status or cron_get_cluster.

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

Usage Guidelines5/5

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

Names two concrete uses (identify the daemon, compare job-set IDs across replicas) and explicitly routes the agent elsewhere: 'use cron_get_cluster for the replicas' roles.' That is an explicit when-to-use plus a named alternative with its condition.

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