Skip to main content
Glama

Explain cron expression

bursia_cron_explain
Read-onlyIdempotent

Explain a 5-field cron expression in plain English and list the next 5 run times (UTC). Pure computation, free.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "expression": "<expression>"
    },
    "name": "bursia_cron_explain"
  }
}

Input Schema

NameRequiredDescriptionDefault
expressionYesA 5-field cron expression: minute hour day-of-month month day-of-week, e.g. "0 9 * * 1-5".

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / expression / description
      Added value: +"A 5-field cron expression: minute hour day-of-month month day-of-week, e.g. \"0 9 * * 1-5\"."
  2. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered; the description adds that computation is local and free and that results are returned in UTC with a fixed count of 5 run times. That UTC scoping and fixed output shape are genuinely new information. It stops short of noting edge cases such as unsupported 6-field/second-precision expressions.

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 action and resource, then the outputs, then the cost/safety qualifier. No filler.

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

Completeness5/5

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

For a single-parameter, annotation-covered, no-output-schema tool, the description supplies what the annotations and schema cannot: what actually comes back (English explanation plus 5 upcoming run times) and the timezone of those run times. Nothing an agent needs before invoking it is missing.

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 description coverage is 100% and the one parameter's schema text already spells out the minute/hour/day-of-month/month/day-of-week layout with an example. The description only restates the '5-field' constraint, adding nothing beyond the schema, so baseline 3 applies.

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?

Specific verb (explain) plus specific resource (a 5-field cron expression) and it even states the two outputs: a plain-English explanation and the next 5 run times. No sibling tool in the list covers cron parsing, so differentiation is effectively implicit rather than stated.

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

Usage Guidelines3/5

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

The single-purpose nature makes the use case self-evident, and 'Pure computation, free' hints that no auth or side effects are involved. However, there is no explicit guidance on when to prefer this over adjacent tools like bursia_timezone_convert or bursia_timestamp_convert, nor any stated input constraints beyond the schema.

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