Skip to main content
Glama
Sign In
MikroMCP

MikroMCP

by AliKarami
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Set System Clock

set_system_clock
DestructiveIdempotent

Set the system date, time, and timezone on a MikroTik router. Use dry-run to preview changes and avoid unintended updates; idempotent calls skip already-matching values.

Instructions

Set the system date, time, and/or timezone on a MikroTik router. Idempotent: returns already_set if the values already match. Supports dry-run.

Input Schema

NameRequiredDescriptionDefault
dateNoDate in RouterOS format: mon/dd/yyyy (e.g. jan/02/2006)
timeNoTime in RouterOS format: hh:mm:ss (e.g. 15:04:05)
dryRunNoPreview changes without applying.
routerIdNoRouter ID; omit to use the default router.
timeZoneNameNoIANA timezone name (e.g. Europe/London, UTC)
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."
    • removedInput schema / required
      Removed value: -[
-  "routerId"
-]
  3. Addedv1.5.0
  4. Removedv1.1.0
  5. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, so the safety profile is covered. The description adds return behavior not present in structured fields — it returns 'already_set' when values already match — which usefully tells the agent the call can short-circuit. It doesn't explain the APPROVAL_REQUIRED/confirmationToken gating or the blast radius of a clock change.

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?

Three compact sentences with the core purpose front-loaded, followed by the two behaviors an agent most needs to know. No filler or restatement of the title.

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?

With no output schema but full schema coverage on six parameters, the description plus schema give an agent what it needs to call correctly. It is nearly complete, though for a destructive tool it could say more about the approval workflow and what a clock/timezone change actually affects.

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 every parameter (including formats, dryRun default, and the confirmationToken semantics) is already documented. The description names the fields being set but adds no format or interaction detail beyond what the schema provides; baseline 3 is appropriate.

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?

States a specific verb (Set) and resource (system date, time, and/or timezone) scoped to a MikroTik router. The 'set' framing cleanly distinguishes it from the read counterpart get_system_clock without needing to open either schema.

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

Usage Guidelines3/5

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

The description implies usage by noting idempotency and dry-run support, which tells an agent it is safe to re-invoke and previewable, but it never states when to reach for this tool versus get_system_clock or how the confirmation/approval flow gates invocation. Usage context is implied rather than explicit.

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