Skip to main content
Glama
Sign In
webmin-mcp-server

webmin-mcp-server

by gjenkins20
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

delete_cron_job

Delete a cron job by providing its index obtained from listing cron jobs.

Instructions

Delete a cron job. This is a dangerous operation and is blocked in safe mode. Use list_cron_jobs to find the job index.

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": {
      "index": "<index>"
    },
    "name": "delete_cron_job"
  }
}

Input Schema

NameRequiredDescriptionDefault
indexYesIndex of the job to delete (from list_cron_jobs)
serverNoServer alias (e.g., 'pi1', 'web-server'). Uses default server if not specified.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior3/5

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

With no annotations, the description carries full burden. It discloses danger and safe mode blocking, but does not mention return values, success/failure behavior, or irreversibility.

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?

Two concise sentences front-load the purpose and key usage guidance, with no unnecessary words. Every sentence is informative.

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 provided, and the description does not specify what the tool returns (e.g., success message, errors). For a mutation tool, return behavior is important context missing.

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

Parameters4/5

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

Schema coverage is 100%, so parameters are documented. The description adds value by explaining how to obtain the index parameter ('Use list_cron_jobs to find the job index'), enhancing understanding beyond the schema.

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 'Delete a cron job' with a specific verb and resource, distinguishing it from sibling tools like create_cron_job and edit_cron_job.

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

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly warns it is dangerous and blocked in safe mode, and advises using list_cron_jobs first to find the index. Provides clear context, though no explicit alternatives to deletion.

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