Skip to main content
Glama

cron-explainer

by io.github.IdoAzaCalls
OverviewDiscussionsAdmin

Server Details

Cron expression parser: explains any cron + returns next N fire times. Timezone-aware.

If you are the author of this connector, you can claim ownership by verifying the domain or GitHub account it belongs to. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
Status
Healthy
Uptime
100.0% over 51 days
Last Tested
Transport
Streamable HTTP · MCP 2025-06-18
URL
Repository
IdoAzaCalls/cron-explainer
GitHub Stars
0
Server Listing
cron-explainer

TDQS

A3.9/5.0

Scored across 1 tool

Disambiguation5/5

Only one tool exists, so there is no ambiguity or risk of misselection. The tool's purpose is clear and distinct.

Naming Consistency5/5

Single tool uses a consistent verb_noun pattern (explain_cron), which is clear and follows common conventions.

Tool Count3/5

With only one tool, the server feels thin for a typical MCP server. While the tool itself is focused, a single tool is borderline for general utility.

Completeness4/5

The tool fully covers the core functionality of explaining a cron expression with fire times and descriptions. However, there are no auxiliary tools for validation or alternative formats, leaving minor gaps.

Available Tools

1 tool
explain_cronAInspect

Parse a POSIX/Vixie cron expression and return the next N fire times plus an English description. Timezone-aware (IANA). Best-effort accuracy. Billed at 1 EUR cent per successful call; non-2xx responses are refunded.

ParametersJSON Schema
NameRequiredDescriptionDefault
nNoNumber of upcoming fire times to return.
tzNoIANA timezone (e.g. 'Europe/Lisbon'). Defaults to UTC.
cronYesPOSIX/Vixie cron expression (5 fields, e.g. '*/15 * * * *').

TDQS

A3.7/5.0
Behavior4/5

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

Discloses timezone awareness, best-effort accuracy, billing cost, and refund policy. With no annotations, this provides essential behavioral context. Could mention error handling for invalid cron 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?

Three sentences cover purpose, features, and billing without redundancy. Each sentence adds unique value, making it highly efficient.

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?

With no output schema, the description should detail return format. It mentions 'next N fire times plus an English description' but lacks specifics on structure or fields, leaving some ambiguity.

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 coverage is 100%, so the schema already describes each parameter. The description adds context for 'tz' (timezone-aware) but does not add new meaning beyond schema for 'cron' or 'n'.

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?

The description clearly states the tool parses a cron expression and returns next fire times with an English description. 'Parse' and 'return' specify action and output, leaving no ambiguity.

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?

No guidance on when to use this tool versus alternatives (none listed). Does not mention prerequisites or context where this tool is appropriate or should be avoided.

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

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 1 tool update
    • First observedexplain_cron

Related MCP Connectors

Related MCP Servers

  • cron-check

    arhancanli
    A
    license
    A
    quality
    B
    maintenance
    Explains cron expressions in plain English, checks them for errors and gotchas, lists next run times in any time zone, and converts between Unix cron, GitHub Actions, Kubernetes, AWS EventBridge, Quartz and Spring dialects.
    3
    MIT

  • Cron Parser API

    Br0ski777
    A
    license
    Not graded
    quality
    D
    maintenance
    Parse, validate, and explain cron expressions with pay-per-call via x402 (USDC on Base L2), returning next run times in any timezone.
    1
    MIT

  • cron-schedule-audit-mcp

    tylerscomic-lab
    A
    license
    Not graded
    quality
    C
    maintenance
    Validates cron expressions and computes DST-correct next-fire times against real IANA timezone data, flagging schedules that silently skip a spring-forward run or double-fire on fall-back. Also surfaces the POSIX day-of-month/day-of-week OR semantics and other semantic footguns before a job ships.
    MIT
Try in Browser
Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources