Skip to main content
Glama
Systems Manager

Systems Manager

Remove Cron Job

sm_cron_remove_cron_job
DestructiveIdempotent

Remove a cron job by its job reference and optional user, with explicit confirmation for mutating changes. Use it to clean up scheduled tasks on managed systems.

Instructions

Remove cron job (sm_cron_operations). Operations for cron jobs

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "sm_cron_remove_cron_job"
  }
}

Input Schema

NameRequiredDescriptionDefault
userNoUser for cron job
confirmNoExplicit confirmation for a mutating action. Pass true when the client cannot answer an approval prompt.
job_refNoOpaque job reference returned by list_cron_jobs

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv2.2.11

TDQS

C2.8/5.0
Behavior2/5

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

Annotations already declare destructiveHint=true, idempotentHint=true, and openWorldHint=true, so the safety profile is fully carried by structured fields. The description adds nothing beyond that — no statement about irreversibility, what happens to an already-removed job, or what confirm actually guards against. It is consistent with the annotations, so no contradiction.

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?

It is short, but the second sentence "Operations for cron jobs" is pure filler that earns no place, and the redundant parenthetical dilutes the front-loaded verb. Size is fine; content density is not.

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 destructive mutation with no output schema, the description should at least signal permanence or the effect of removal. Annotations cover the safety flags and the schema covers the parameters, but the description itself leaves the agent without any behavioral framing for an irreversible action.

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 description coverage is 100%, with all three parameters (user, confirm, job_ref) documented in the schema itself, including that job_ref is an opaque reference from list_cron_jobs. The description adds no parameter-level meaning, so the baseline 3 applies.

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?

"Remove cron job" states a specific verb and resource, which is enough to tell it apart from the listing sibling sm_cron_list_cron_jobs. The trailing parenthetical "(sm_cron_operations)" and "Operations for cron jobs" add no distinguishing information, but the core statement is clear.

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?

The description gives no when-to-use guidance, no prerequisites, and no mention of any alternative (e.g., that job_ref comes from list_cron_jobs, which only the schema reveals). An agent must infer everything about invocation context from the schema and annotations.

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

Deploy Server

Other Tools