Skip to main content
Glama
Sign In

GadgetHumans API Hub

by com.gadgethumans
OverviewDiscussionsAdmin

cron_parse

Explain a cron expression in plain English and return the next scheduled run times. Pure CPU, instant. Use to verify a schedule before deploying it.

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": {
      "cron": "<cron>"
    },
    "name": "cron_parse"
  }
}

Input Schema

NameRequiredDescriptionDefault
cronYesCron expression
countNoHow many next runs

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added
  2. Removed
  3. Changed3 schema fields changed
    • addedInput schema / properties / count
      Added value: +{
+  "description": "How many next runs",
+  "type": "integer"
+}
    • addedInput schema / properties / cron
      Added value: +{
+  "description": "Cron expression",
+  "type": "string"
+}
    • addedInput schema / required
      Added value: +[
+  "cron"
+]
  4. Added

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does disclose useful traits: 'Pure CPU, instant' signals a deterministic, side-effect-free, low-latency operation, and the return content is stated. It stops short of describing what happens with a malformed expression or what the default for the run count is.

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 short sentences, front-loaded with the core action and output before the operational note and the usage hint. No sentence is redundant; 'Pure CPU, instant' earns its place as the only behavioral signal available without annotations.

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?

With no output schema, the description does its job by naming both return components (plain-English explanation and upcoming run times). The gap is that the shape of the output and the default value of 'count' are left unspecified for an otherwise simple two-parameter tool.

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 description coverage is 100%, so both parameters are already documented ('Cron expression', 'How many next runs'). The description implies the two parameters through 'explain a cron expression' and 'next scheduled run times' but adds no syntax examples, accepted cron dialects, or default/limit for count.

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 names a specific verb and resource ('Explain a cron expression') and states the return content ('next scheduled run times'). No sibling tool in the list handles cron expressions, so no differentiation is needed and an agent can identify the function immediately.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives an explicit usage scenario: 'Use to verify a schedule before deploying it.' There are no sibling alternatives to route against, so no exclusions are needed, but the guidance is limited to that single scenario rather than covering other cases such as debugging an existing job.

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

All GadgetHumans API Hub toolsInspect
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.

Resources