A
license-
qualityC
maintenanceProvides tools to parse and describe cron expressions in plain English, and compute future run times.
Last updated
12
MIT
cron-explainer
Server Details
Cron expression parser: explains any cron + returns next N fire times. Timezone-aware.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- IdoAzaCalls/cron-explainer
- GitHub Stars
- 0
- Server Listing
- cron-explainer
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
MCP client
Glama
MCP server
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
100% free. Your data is private.
Tool Definition Quality
A3.9/5.0
Tool DescriptionsA
Average 3.7/5 across 1 of 1 tools scored.
Server CoherenceA
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 toolexplain_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
| Name | Required | Description | Default |
|---|---|---|---|
| n | No | Number of upcoming fire times to return. | |
| tz | No | IANA timezone (e.g. 'Europe/Lisbon'). Defaults to UTC. | |
| cron | Yes | POSIX/Vixie cron expression (5 fields, e.g. '*/15 * * * *'). |
Tool Definition Quality
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.
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!
Related MCP Servers
- Alicense-qualityBmaintenanceParse, validate, and explain cron expressions with pay-per-call via x402 (USDC on Base L2), returning next run times in any timezone.Last updated1MIT
- Alicense-qualityDmaintenanceEnables exploration, explanation, and management of crontab entries, including translating cron expressions into plain English and calculating upcoming execution times.Last updated4MIT
- AlicenseAqualityCmaintenanceEnables AI agents to parse, validate, explain, and preview cron expressions, surfacing common silent bugs before deployment.Last updated427MIT
Try in Browser
Your Connectors
Sign in to create a connector for this server.