Skip to main content
Glama
Sign In
MikroMCP

MikroMCP

by AliKarami
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Manage DHCP Client

manage_dhcp_client
DestructiveIdempotent

Add, remove, enable, or disable a DHCP client on a network interface. Idempotent by interface name to avoid duplicate configurations.

Instructions

Add, remove, enable, or disable a DHCP client on an interface. Idempotent by interface name: add returns already_exists if a DHCP client is already configured on the same interface.

Input Schema

NameRequiredDescriptionDefault
actionYesAction to perform
dryRunNoPreview changes without applying.
commentNoOptional comment (add only)
routerIdNoRouter ID; omit to use the default router.
interfaceYesInterface name — idempotency key (e.g. ether1); for remove/enable/disable a client's display name also matches
usePeerDnsNoUse DNS servers provided by DHCP server (add only)
usePeerNtpNoUse NTP servers provided by DHCP server (add only)
addDefaultRouteNoAdd default route from DHCP (add only)
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.16.0
    • changedInput schema / properties / interface / description
      Previous value: -"Interface name — idempotency key (e.g. ether1, ether2)"New value: +"Interface name — idempotency key (e.g. ether1); for remove/enable/disable a client's display name also matches"
  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",
-  "interface"
-]New value: +[
+  "action",
+  "interface"
+]
  3. Addedv1.5.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare destructiveHint, idempotentHint, and non-readOnly, so the bar is lower. The description adds real value beyond them: it names the idempotency key (interface name) and discloses the already_exists return on duplicate add, which the annotations only imply abstractly.

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 sentences, zero waste. The action scope is front-loaded and the idempotency caveat follows immediately as the secondary point an agent needs.

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 destructive 9-parameter tool with no output schema, the description plus annotations and a fully documented schema cover what an agent needs to call it. It does not mention the APPROVAL_REQUIRED/confirmationToken flow, but the schema parameter description carries that detail adequately.

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 every parameter including the interface idempotency key, dryRun, and confirmationToken. The description restates the interface-key semantics rather than adding new meaning, so baseline 3 applies.

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 (add, remove, enable, disable) against a specific resource (DHCP client on an interface). This is clearly distinguishable from siblings like manage_dhcp_server, manage_dhcp_lease, and list_dhcp_clients without opening the 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?

Use is implied by the enumerated actions, but there is no explicit guidance on when to choose this over siblings (e.g., manage_dhcp_server, manage_dhcp_lease) or when to pair it with plan_changes/dryRun. The already_exists note is a behavioral hint rather than a usage rule.

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