APIVerve

Cron Expression Generator

CronExpressionGenerator

Read-only

Cron Expression Generator: Cron Expression Generator converts natural language schedule text into standard five-field cron expressions. Submit phrases up to 200 characters to receive the matching cron syntax, with paid plans adding written explanations. (Cost: 10 credits)

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": {
      "schedule": "<schedule>"
    },
    "name": "CronExpressionGenerator"
  }
}

Input Schema

Name	Required	Description	Default
`schedule`	Yes	Natural language description of the schedule (max 200 characters)

Output Schema

Name	Required	Description
`data`	No
`error`	No	Error message, null on success
`status`	No	"ok" on success

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 7, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already cover safety (readOnlyHint=true, destructiveHint=false, openWorldHint=true). The description adds genuinely new behavioral context: a 10-credit cost per call and that written explanations are gated behind paid plans, which an agent should know before invoking.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Effectively two sentences, front-loaded with the core function and then the input constraint and cost. Minor waste: the title is repeated verbatim at the start ('Cron Expression Generator: Cron Expression Generator ...').

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

Completeness4/5

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

For a one-parameter read-only generator with an output schema and full annotation coverage, the description supplies what's missing: input limit, cost, and output tiering. Only accepted phrasing patterns or failure behavior on unparseable input are left unaddressed.

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% for the single required 'schedule' parameter, so the schema already documents type, example, and the 200-character cap. The description restates the same length limit and adds no new syntax guidance on what phrasing formats are accepted.

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?

States a specific verb and resource: converts natural language schedule text into standard five-field cron expressions. The direction of conversion is explicit, which distinguishes it from the inverse sibling CronExpressionParser without needing to name it.

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?

Gives an implied usage context (submit natural-language phrases) and an input bound of 200 characters, but offers no when-to-use versus when-not guidance and no mention of alternatives such as CronExpressionParser for the reverse direction.

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

All APIVerve tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.