Skip to main content
Glama

create_job

Creates a new cron job on a specified machine with a name, cron schedule, command, and optional enabled status.

Instructions

Create a new cron job on a machine.

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": {
      "machine_id": "<machine_id>",
      "name": "<name>",
      "schedule": "<schedule>",
      "command": "<command>"
    },
    "name": "create_job"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
commandYes
enabledNo
scheduleYesCron expression, e.g. "0 * * * *"
machine_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.3

TDQS

C2.6/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden and discloses almost nothing: it does not say whether the job starts running immediately, what the default for 'enabled' is, whether creation is idempotent, or what permissions/scope are needed. 'Create' does convey a mutation, but for a state-changing tool with zero annotation coverage this is a significant gap.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The single sentence is front-loaded and free of filler, but its brevity is under-specification rather than economy — trimming here has cost the definition needed detail rather than saved anything.

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?

For a 5-parameter write operation with no annotations, no output schema, and sparse schema documentation, the definition is far too thin: an agent learns what resource is created but not its required inputs' meaning, its side effects, or its failure modes.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 5 parameters and only 20% schema description coverage, the description must compensate and does not — it never explains what name, command, machine_id, or enabled mean, nor that enabled is optional while the other four are required. The phrase 'on a machine' only faintly gestures at machine_id.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb and resource ('Create a new cron job') scoped to 'a machine,' which is enough to distinguish it from sibling mutations like update_job and delete_job. It stops short of differentiating itself explicitly from any sibling, so it is clear rather than exemplary.

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?

There is no guidance on when to call this versus update_job or sync_jobs, no mention of required preconditions (does the machine have to exist? does sync need to run afterward?), and no statement of what happens if a job of the same name already exists.

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