Skip to main content
Glama
AliKarami

MikroMCP

by AliKarami
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Manage DHCP Lease

manage_dhcp_lease
DestructiveIdempotent

Convert a dynamic DHCP lease to static or remove a lease by MAC address, with optional dry-run preview before applying changes.

Instructions

Convert a dynamic DHCP lease to static (make-static) or remove a lease. Idempotent by MAC address.

Input Schema

NameRequiredDescriptionDefault
actionYesAction to perform: make-static converts a dynamic lease to static; remove deletes the lease
dryRunNoPreview changes without applying.
routerIdNoRouter ID; omit to use the default router.
macAddressYesMAC address of the lease — idempotency key (case-insensitive)
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",
-  "macAddress"
-]New value: +[
+  "action",
+  "macAddress"
+]
  3. Addedv1.5.0

TDQS

A3.8/5.0
Behavior3/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 structurally. The description adds one useful detail beyond them — idempotency is keyed specifically to MAC address — but omits the two-step APPROVAL_REQUIRED/confirmationToken workflow and any note that 'remove' is irreversible.

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 compact sentences with zero filler; the primary operation is front-loaded, and the second sentence delivers the key operational invariant immediately.

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?

For a 5-parameter mutation tool with full schema coverage, no output schema, and annotations carrying the safety profile, the description is largely sufficient. It is slightly thin on the confirmation/approval flow and dryRun interplay, though those are spelled out in the schema.

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 all five parameters (action, dryRun, routerId, macAddress, confirmationToken) are already documented in the schema; baseline 3 applies. The description's 'idempotent by MAC address' marginally reinforces macAddress semantics but adds no new syntax or format detail.

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 names the resource (DHCP lease) and the two concrete operations (convert dynamic→static, remove), matching the enum values exactly. An agent can distinguish it from sibling list_dhcp_leases, manage_dhcp_server, and manage_dhcp_client without opening any 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?

Usage is implied by the action names, but there is no explicit when-to-use or when-not-to-use guidance, nor any pointer to alternatives (e.g. list_dhcp_leases for discovery before mutating). The destructive path and its confirmation requirement are left entirely to the schema.

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