Skip to main content
Glama
AliKarami

MikroMCP

by AliKarami
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Manage Scheduled Job

manage_scheduled_job
DestructiveIdempotent

Add, update, remove, enable, or disable RouterOS scheduled jobs by name. Preview changes with dry-run before applying router automation scripts.

Instructions

Add, update, remove, enable, or disable a RouterOS scheduler entry. onEvent is arbitrary RouterOS script run with the router user's policies, so this tool is destructive. Idempotent by name. add throws CONFLICT if name exists; update throws NOT_FOUND if it does not. Supports dry-run.

Input Schema

NameRequiredDescriptionDefault
nameYesJob name — idempotency key
actionYesAction to perform
dryRunNoPreview changes without applying.
commentNoOptional comment
onEventNoScript name or inline command to run (required on add)
intervalNoRun interval (e.g. 00:05:00 for every 5 minutes)
routerIdNoRouter ID; omit to use the default router.
startDateNoStart date (e.g. jan/01/2000)
startTimeNoStart time (e.g. 00:00:00)
confirmationTokenNoToken from a prior APPROVAL_REQUIRED response. Re-submit the identical call with this token to confirm the destructive action.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.14.1
    • addedInput schema / properties / confirmationToken
      Added value: +{
+  "description": "Token from a prior APPROVAL_REQUIRED response. Re-submit the identical call with this token to confirm the destructive action.",
+  "type": "string"
+}
  2. Changed3 schema fields changedv1.6.0
    • changedInput schema / properties / dryRun / description
      Previous value: -"Preview changes without applying"New value: +"Preview changes without applying."
    • changedInput schema / properties / routerId / description
      Previous value: -"Target router identifier from the router registry"New value: +"Router ID; omit to use the default router."
    • changedInput schema / required
      Previous value: -[
-  "routerId",
-  "action",
-  "name"
-]New value: +[
+  "action",
+  "name"
+]
  3. Addedv1.5.0
  4. Removedv1.1.0
  5. First observedv0.1.0

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, but the description explains WHY: onEvent is arbitrary RouterOS script executed with the router user's policies, which is the concrete blast radius. It also discloses per-action error contracts and dry-run support, adding real value beyond the structured hints.

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?

Four tight sentences, no filler, and the destructive-risk rationale plus error semantics are front-loaded right after the verb list. Every sentence carries distinct information.

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

Completeness4/5

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

No output schema exists, and the description covers the mutation's risks, idempotency model, error cases, and dry-run. It leaves partial-update behavior on 'update' (whether omitted fields are preserved) and the enable/disable preconditions unstated, which is a modest gap for a 10-parameter destructive tool.

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%, so the schema already documents name, action enum, dryRun, confirmationToken, and timing fields; baseline is 3. The description's semantic additions ('idempotent by name', onEvent policy context) largely restate or slightly extend what the schema already says, especially since 'Job name — idempotency key' is already in 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?

Opens with a specific multi-verb statement of the resource acted upon: 'Add, update, remove, enable, or disable a RouterOS scheduler entry.' The agent can immediately separate this mutating tool from the read-only sibling list_scheduled_jobs without opening a schema.

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?

Gives clear operational conditions: idempotency by name, add throws CONFLICT on existing names, update throws NOT_FOUND on missing ones, and dry-run is supported. It never explicitly routes the agent to list_scheduled_jobs for reads or states when-not-to-use, so it stops short of full when/alternatives guidance.

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