Generate cron schedule expressions by specifying minute, hour, day of month, month, and day of week fields.
Generate crontab expressions
| Name | Required | Description | Default |
|---|---|---|---|
| minute | No | Minute (0-59, *, */n, n-m) | |
| hour | No | Hour (0-23, *, */n, n-m) | |
| dayOfMonth | No | Day of month (1-31, *, */n, n-m) | |
| month | No | Month (1-12, *, */n, n-m) | |
| dayOfWeek | No | Day of week (0-7, *, */n, n-m) |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations provide readOnlyHint=false, indicating mutation, but the description adds no behavioral context beyond 'generate'. No disclosure of what the output looks like or side effects, leaving the agent guessing.
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, concise sentence with no wasted words. It is appropriately short but could benefit from slightly more structure or clarity.
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?
The tool has no output schema, and the description does not explain the return value or format. With 5 optional parameters, the agent lacks context on default behavior or expected output, making it incomplete.
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?
Input schema covers all parameters with descriptions, so schema_description_coverage is 100%. The description adds no extra meaning beyond what is already in the schema, baseline of 3.
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 generates crontab expressions, using a specific verb and resource. However, it lacks differentiation from sibling tools like generate_password, but the unique purpose is evident.
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?
No guidance on when to use this tool versus alternatives or any context about its applicability. The description is too brief to help an agent decide when to invoke it.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/wrenchpilot/it-tools-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server