Skip to main content
Glama

create_dhcp_server

Creates a DHCP server on a MikroTik device and binds it to a specified interface, with optional lease time, address pool, and authoritative settings.

Instructions

Creates a DHCP server bound to the specified interface on the MikroTik device.

Notes: lease_time: duration e.g. "1d", "12h", "30m", "1h30m"

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": {
      "name": "<name>",
      "interface": "<interface>"
    },
    "name": "create_dhcp_server"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
deviceNo
commentNo
disabledNo
interfaceYes
lease_timeNo1d
address_poolNo
authoritativeNoyes
delay_thresholdNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.14.5
    • addedInput schema / properties / device
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "title": "Device"
      +}
  2. First observedv0.0.0

TDQS

C2.7/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false, and openWorldHint=false, so the safety profile is largely covered. The description adds nothing beyond that — it does not warn that repeated calls create duplicate servers (idempotentHint=false), nor describe what happens when the interface or pool is missing, nor whether the server is enabled immediately (disabled defaults to false).

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The core action is front-loaded in one sentence, followed by a compact note. There is no filler, though the single note is a thin payload for the amount of space given.

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?

With 9 parameters, zero schema coverage, and an output schema that relieves it of return-value explanation, the description should explain at minimum the address_pool/interface relationship and the non-idempotent creation behavior. It does neither, leaving an agent to guess at the most consequential inputs.

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

Parameters2/5

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

Schema description coverage is 0% across 9 parameters, so the description carries the full burden — yet it explains only lease_time's duration syntax. Key fields like address_pool, authoritative (yes/no/after-2sec-delay), delay_threshold, and device are left entirely unexplained, which is a significant gap for a creation tool.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Creates a DHCP server') plus a scoping constraint ('bound to the specified interface on the MikroTik device'), which loosely separates it from create_dhcp_network and create_dhcp_pool. It does not explicitly name a sibling it is not, so it stops short of the top score.

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

Usage Guidelines2/5

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

There is no when-to-use guidance and no mention of prerequisites, such as whether the interface or referenced address pool must already exist, or whether create_dhcp_pool/create_dhcp_network should be called first. The only 'Note' concerns a parameter format, not usage context.

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