Skip to main content
Glama

devops-linux

cron_explain_and_schedule

Validate a 5-field POSIX cron expression, translate it into human English, and compute its next N UTC firing timestamps.

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

Input Schema

NameRequiredDescriptionDefault
textNo
countNo
expressionNoe.g. "*/15 * * * *"

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden. It usefully discloses that timestamps are UTC and that the expression is validated, but it never says what happens on an invalid expression (error versus explanatory message), whether validation and scheduling are one call or separable, or what the response structure looks like.

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?

One sentence, front-loaded with the validation action and carrying all three operations without padding. Every clause earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 3-parameter tool with no annotations and no output schema, the description covers the operations and timezone but omits the two things an agent most needs: which string parameter to populate and what the return/error shape is.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 33% — only `expression` is documented (with an example), while `text` and `count` are bare. Worse, the description never explains the difference between `text` and `expression`, an ambiguity an agent must resolve before calling. This is a case where the description should have compensated for low coverage and does not.

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 uses specific verbs and a precise resource: validate a 5-field POSIX cron expression, translate it to English, and compute next N UTC firing timestamps. An agent knows exactly what the tool does. Sibling differentiation is moot here since the catalog contains no other cron tool, but nothing in the text frames it against alternatives, so it falls just 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?

There is no when-to-use guidance, no prerequisites, and no mention of when not to use it or what to use instead. The description states capability only, leaving the agent to infer that this is the tool for cron parsing versus the config-linting siblings.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources