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
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
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.
Tool Definition Quality
Average 4/5 across 1 of 1 tools scored.
Only one tool exists, so there is no ambiguity with other tools. The tool's purpose is clearly described.
With a single tool, naming consistency cannot be assessed meaningfully; it follows a reasonable verb_noun pattern.
A single tool is too few for a server; it suggests either an extremely narrow domain or a micro-service that could be merged into a larger server.
The tool only explains cron expressions, but does not allow creating, modifying, or deleting cron jobs. For the domain of cron management, this is severely incomplete.
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.
| 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
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description must disclose behavioral traits. It mentions timezone-awareness, best-effort accuracy, and billing. However, it doesn't state what happens on invalid cron syntax (error message?), rate limits, or if it requires authentication. With no annotations, this is adequate but not thorough.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is very concise: three sentences, each serving a distinct purpose (function, timezone, billing). No wasted words. Front-loaded with the primary action.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the parameter count (3) and no output schema, the description covers the core purpose, timezone handling, and billing. It doesn't mention possible errors, but for a simple parsing tool, this may be sufficient. The absence of output schema means the description could hint at the output format, but it doesn't, which is a minor gap.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, so the schema already describes all parameters well. The description doesn't add much beyond what's in the schema, but it does provide context for the overall tool (e.g., timezone-awareness). Baseline 3 is appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
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, returns next N fire times, and gives an English description. It specifies it's timezone-aware and mentions billing. The verb 'parse' and product 'cron expression' are specific, and the tool name 'explain_cron' directly reflects this.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description tells the user when to use this tool (to parse a cron expression and get upcoming fire times). It doesn't explicitly mention when not to use it or list alternatives, but since there are no sibling tools, this is acceptable. The billing info gives implicit guidance that failures are refunded.
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!