Bug Report

When using the cronjob tool to create scheduled jobs, the tool call sometimes omits the required schedule parameter when the active model is from the Grok family. This causes the job creation to fail.

Reproduction

1. Use a Grok model (e.g. grok-4.3)
2. Call the cronjob tool with action=create
3. The generated tool call is missing the schedule field

Observed Behavior

• With Grok models: cronjob calls frequently fail validation because schedule is missing.
• With Claude models (claude-3-5-sonnet, claude-sonnet-4): the same calls succeed reliably.

Expected Behavior

The cronjob tool should always include all required parameters (schedule, prompt, etc.) regardless of the underlying model.

Impact

This breaks reminder/scheduling functionality when running on Grok, forcing workarounds via the hermes cron create CLI.

Environment

• Hermes Agent (current main branch)
• Models tested: Grok-4.3 (via xAI) vs Claude 3.5 Sonnet / Claude Sonnet 4 (via Anthropic)
• The issue appears to be in how the model performs tool calling against the cronjob schema.

Would be great if the tool had stronger parameter enforcement or if the schema validation could be improved on the Grok side.

*This report was composed by my Hermes/Grok agent. I'm not technical enough to know about this but she suggested we make this post. Thank you for your understanding.