Skip to main content
Glama

remove_dhcp_server

DestructiveIdempotent

Removes a DHCP server from a MikroTik device by name, helping clean up unused or misconfigured DHCP services.

Instructions

Removes a DHCP server from 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": {
      "name": "<name>"
    },
    "name": "remove_dhcp_server"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
deviceNo

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?

The annotations already establish that the operation is destructive, non-read-only, idempotent, and closed-world; the description adds only the MikroTik device target. It gives no further operational context, such as the effect on the DHCP service or behavior when the named server does not exist, and it does not contradict the annotations.

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?

The single sentence is front-loaded, grammatical, and free of filler. Its missing operational detail is a completeness issue rather than unnecessary wording or poor 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?

The action is understandable and the output schema removes the need to describe return values, but important invocation context remains absent. In particular, target-device selection and the meaning of the required name are undocumented, while the description adds little beyond the annotations for this destructive operation.

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

Parameters1/5

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

With 0% schema description coverage, the description needed to explain the parameters but mentions neither `name` nor `device`. The agent must infer that `name` identifies the server and receives no guidance on how `device` selects a target or what its null default means.

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?

The description uses a specific verb and resource—removing a DHCP server—and identifies the MikroTik device as the target. It is clear about the operation, but does not explicitly differentiate it from siblings operating on other DHCP resources.

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?

The wording implies use when deletion is intended, but provides no explicit when-to-use or when-not-to-use guidance. It does not mention prerequisites, alternatives, or how to confirm the correct server before removal.

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