Skip to main content
Glama

create_dhcp_network

Configures a DHCP network on a MikroTik device by setting gateway, DNS, domain, and related options to automate client IP address assignment.

Instructions

Creates a DHCP network configuration (gateway, DNS, domain, etc.) on the MikroTik device.

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": {
      "network": "<network>",
      "gateway": "<gateway>"
    },
    "name": "create_dhcp_network"
  }
}

Input Schema

NameRequiredDescriptionDefault
deviceNo
domainNo
commentNo
gatewayYes
netmaskNo
networkYes
dhcp_optionNo
dns_serversNo
ntp_serversNo
wins_serversNo

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.9/5.0
Behavior2/5

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

Annotations already carry the full behavioral profile (readOnlyHint=false, destructiveHint=false, idempotentHint=false, openWorldHint=false). The description adds essentially nothing beyond the name: it does not say whether duplicate network definitions are rejected, what permissions or device targeting are needed, or what happens on failure.

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?

A single front-loaded sentence with the verb and resource first and no padding. The trailing 'etc.' is the only filler, which slightly weakens an otherwise tight structure.

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?

An output schema covers return values, but for a 10-parameter mutation tool with zero schema descriptions the definition is far too thin. An agent cannot tell what 'network' versus 'netmask' should contain, or how the optional server lists and dhcp_option behave.

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 10 parameters, so the description must compensate and largely does not. It names gateway, DNS and domain only, leaving network, netmask, dhcp_option, ntp_servers, wins_servers, device, and comment completely unexplained; the 'etc.' hides rather than resolves the ambiguity.

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 ('Creates') and resource ('DHCP network configuration') and lists representative fields (gateway, DNS, domain). It distinguishes the resource from create_dhcp_server and create_dhcp_pool implicitly, but never names or contrasts them, so an agent must infer the boundary.

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 verb 'Creates' implies the appropriate context (provisioning a new DHCP network), but there is no explicit when-to-use guidance, no mention of how it differs from update_dhcp_network or create_dhcp_server, and no prerequisites or ordering advice.

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