Generate a cron expression from human-friendly options.
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": {
"every": "<every>"
},
"name": "generate_cron"
}
}| Name | Required | Description | Default |
|---|---|---|---|
| at | No | ||
| on | No | ||
| every | Yes | Frequency | |
| month | No | Month (1-12) |
Changes observed during successful MCP inspections.
Input schema / properties / on / properties / date / descriptionAdded value: +"1-31"Input schema / properties / on / properties / day / descriptionAdded value: +"0=Sunday"Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are present, so the description carries the full burden of behavioral disclosure. It does not mention the return format, validation behavior, how conflicting options are resolved, or any error cases, offering only a high-level action statement.
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 a single, front-loaded sentence with no redundant wording. However, it is so brief that it borders on under-specification, though it remains clean and appropriately compact for its core purpose.
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 four parameters, nested objects, no output schema, and no annotations, the description is severely under-powered. It offers no examples, constraints on parameter combinations, or explanation of what constitutes a valid cron expression, making it incomplete for reliable tool invocation.
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?
The description does not add meaning to any specific parameter beyond the generic phrase 'human-friendly options.' With schema description coverage at 50% and nested objects like 'at' lacking descriptions, the description should compensate but does not, leaving parameter semantics incomplete.
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 a specific action ('Generate a cron expression') and the input source ('human-friendly options'). This distinctly separates it from sibling tools like validate_cron or explain_cron, which imply different operations on cron expressions.
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 provides no guidance on when to use this tool versus alternatives. There are no scenarios, prerequisites, or mentions of sibling tools, leaving the agent to infer usage context from the name alone.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.