Skip to main content
Glama

nexo_schedule_add

Add a personal cron job by automatically creating a LaunchAgent (macOS) or systemd timer (Linux) with execution tracking.

Instructions

Add a new personal cron job. Creates LaunchAgent (macOS) or systemd timer (Linux) automatically, wrapped with execution tracking.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cron_idYesUnique ID for this cron (e.g. 'my-backup', 'report-daily'). Must be lowercase with hyphens.
scriptYesPath to the script to run (absolute or relative to personal/scripts/).
scheduleNoTime-based schedule as 'HH:MM' (daily) or 'HH:MM:weekday' (e.g. '08:00:1' for Monday 8AM). Mutually exclusive with interval_seconds.
interval_secondsNoRun every N seconds (e.g. 300 for every 5 min). Mutually exclusive with schedule/keep_alive.
descriptionNoWhat this cron does (for logs and status).
script_typeNo'auto' (default), 'python', 'shell', 'node', or 'php'.auto
keep_aliveNoRun as a daemon/keep-alive service instead of a timer.
Behavior3/5

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

Discloses automatic creation of LaunchAgent/systemd timer and execution tracking, but lacks details on side effects (e.g., overwriting existing cron jobs, permission requirements) and error handling. Without annotations, more behavioral context is needed.

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?

Single sentence of 23 words, front-loads key purpose and mechanism. No wasted words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema and no mention of return value, success confirmation, or error conditions. For a tool with 7 parameters and no output schema, the description should cover these aspects to be complete.

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 coverage is 100%, so baseline 3. Description adds no extra parameter-specific meaning beyond what the schema already provides.

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 clearly states 'Add a new personal cron job' with specific verb and resource, and distinguishes from sibling tools by specifying 'personal' and automatic system service creation. It is unambiguous.

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

Usage Guidelines2/5

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 like nexo_automation_schedule or nexo_core_schedule_set. No prerequisites or exclusions mentioned.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/wazionapps/nexo'

If you have feedback or need assistance with the MCP directory API, please join our Discord server