Skip to main content
Glama

update_dhcp_network

Idempotent

Modifies an existing DHCP network entry on a MikroTik device, letting you update gateway, netmask, DNS/NTP/WINS servers, domain, and DHCP options or clear selected fields.

Instructions

Updates fields on an existing DHCP network entry on the MikroTik device.

Notes: Pass an empty list for dns_servers/wins_servers/ntp_servers/dhcp_option (or "" for domain) to clear that field.

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>"
    },
    "name": "update_dhcp_network"
  }
}

Input Schema

NameRequiredDescriptionDefault
deviceNo
domainNo
commentNo
gatewayNo
netmaskNo
networkYes
dhcp_optionNo
dns_serversNo
ntp_serversNo
wins_serversNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.19.4

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=true, and openWorldHint=false, so the safety profile is covered. The description adds genuinely useful behavior beyond that: passing an empty list/string clears a field. It does not state what null does for the other optional parameters (presumably leave unchanged), which is the single most consequential behavioral detail for a partial-update tool.

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?

Two sentences, front-loaded with purpose, followed by a clearly separated notes block on clearing semantics. No wasted wording, though the note is terse relative to the number of undocumented parameters.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return values need no explanation. However, for a 10-parameter mutation tool with zero schema description coverage, the description leaves key calling semantics (identifier field, null-versus-clear behavior, device targeting) to inference.

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 carry the semantic load. It only explains clearing behavior for dns_servers, wins_servers, ntp_servers, dhcp_option, and domain, and says nothing about the required 'network' identifier, 'device' selection, 'gateway', 'netmask', or 'comment'.

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: "Updates fields on an existing DHCP network entry on the MikroTik device." That clearly distinguishes it from create_dhcp_network and remove_dhcp_network by name alone, though it does not explicitly call out those siblings.

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?

No explicit when-to-use versus when-to-use-an-alternative statement and no prerequisites (e.g., the network entry must already exist). The phrase "existing DHCP network entry" implies it is a modification path rather than creation, so usage is only implied.

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