Cron parser | agent view
The same page content and links, with explicit tool capabilities. Tools marked with an API can run directly through HTTP. Other tools require the browser interface or are not connected yet.
Tool capabilities
{
"id": "cron-parser",
"category": "developer-tools",
"built": true,
"requirements": "Cron dialect and time-zone selection; show next runs and daylight-saving ambiguity.",
"implementation": {
"fields": [
{
"key": "zone",
"label": "IANA time zone",
"value": "UTC",
"type": "text"
},
{
"key": "start",
"label": "Start ISO date (blank = now)",
"value": "",
"type": "text"
},
{
"key": "n",
"label": "Next occurrences",
"value": 10,
"type": "number"
}
],
"experience": {
"automatic": false,
"single": true,
"label": "Cron expression",
"placeholder": "0 9 * * 1",
"help": "Enter a cron expression and choose the time zone below. Up to 1,000,000 characters. Review the settings before running.",
"action": null
},
"mode": "explicit",
"interactive": false
},
"execution": "POST /api/v1/tools/cron-parser/run",
"api": {
"id": "cron-parser",
"name": "Cron parser",
"category": "developer-tools",
"description": "Cron dialect and time-zone selection.",
"notes": "",
"human_path": "/en/developer-tools/cron-parser/",
"method": "POST",
"endpoint": "/api/v1/tools/cron-parser/run",
"schema_url": "/api/v1/tools/cron-parser",
"input_schema": {
"type": "object",
"additionalProperties": false,
"properties": {
"input": {
"type": "string",
"maxLength": 1000000,
"default": "",
"description": "Plain text input. File tools use files instead unless otherwise documented."
},
"options": {
"type": "object",
"additionalProperties": false,
"properties": {
"zone": {
"type": "string",
"description": "IANA time zone",
"default": "UTC"
},
"start": {
"type": "string",
"description": "Start ISO date (blank = now)",
"default": ""
},
"n": {
"type": "number",
"description": "Next occurrences",
"default": 10.0
}
}
}
}
},
"output_schema": {
"type": "object",
"required": [
"tool",
"result"
],
"properties": {
"tool": {
"type": "string"
},
"result": {
"type": "object",
"required": [
"text",
"files"
],
"properties": {
"text": {
"type": [
"string",
"null"
]
},
"data": {
"description": "Parsed JSON when the textual result is JSON."
},
"name": {
"type": "string"
},
"mime": {
"type": "string"
},
"files": {
"type": "array",
"items": {
"type": "object",
"required": [
"name",
"mime",
"bytes",
"base64"
],
"properties": {
"name": {
"type": "string"
},
"mime": {
"type": "string"
},
"bytes": {
"type": "integer"
},
"base64": {
"type": "string",
"contentEncoding": "base64"
}
}
}
}
}
}
}
},
"processing": "Server; same transformation code as browser tools",
"limits": {
"request_bytes": 8388608,
"input_characters": 1000000,
"files_bytes": 5242880,
"max_files": 0,
"timeout_seconds": 12
}
},
"agent_processing": "Server; same transformation code as browser tools",
"browser_agent": {
"supported": true,
"name": "run_current_tool",
"discovery": "WebMCP on the human page in a supporting browser",
"verification": "See audit/API-AUDIT.md; availability is not verification"
}
}Page guide
Cron dialect and time-zone selection.
Useful next steps
How to use Cron parser
- Enter cron expression in the input field.
- Review the settings, then choose Run Cron parser.
- Review the result, then use Copy result or a download link when available.
Working with cron parser
Formatting makes existing data or code easier to read. Validation checks whether it follows a syntax or schema. Conversion maps it into another representation. Choosing the right operation helps avoid treating a neatly formatted result as proof that the underlying data is correct.
Common questions
Does valid JSON mean the data is correct?
Syntax validation only establishes that the text can be parsed as JSON. A schema can check required fields and types, but neither proves that an email address, price or external record is factually correct.
Is decoding the same as decrypting or verifying?
No. Base64 and URL encoding are representations, not encryption. Reading a token payload does not verify its signature. Use the specific validation or verification process required by the system receiving the result.
Continue your workflow: JSON schema validator, Jsonpath tester, YAML formatter.