Skip to main content
Glama

remove_static_ip

Destructive

Remove a device's fixed IP reservation by MAC address, previewing the change first and applying it only when confirmed.

Instructions

Remove a device's fixed IP reservation. Without confirm=true it only shows the plan.

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": {
      "mac": "<mac>"
    },
    "name": "remove_static_ip"
  }
}

Input Schema

NameRequiredDescriptionDefault
macYes
confirmNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.8/5.0
Behavior4/5

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

The annotations declare destructiveHint=true, but they do not reveal that the default path is a non-destructive dry run. The description supplies exactly that, which is high-value context for a destructive tool. It omits what the plan output looks like or what happens if the reservation does not exist, keeping it from a 5.

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 short sentences, front-loaded with the action and then the safety constraint. Every clause carries information an agent needs; nothing is padded.

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 two-parameter destructive tool with no output schema, the description covers the critical safety behavior and the commit switch. The remaining gap is how to identify the target device via 'mac', which is left entirely to an undocumented schema field.

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 0%, so the description must carry parameter meaning. It fully explains 'confirm' (default false means preview-only), but adds nothing about 'mac' — no format, no indication whether it is the device MAC or reservation identifier. Half the parameters are therefore still undocumented.

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: 'Remove a device's fixed IP reservation.' That clearly distinguishes it from set_static_ip without needing the schema. It stops short of explicitly naming the inverse sibling, so it lands just below a 5.

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 description implies the intended usage pattern ('Without confirm=true it only shows the plan'), which tells the agent this is a two-step preview-then-commit operation. It does not say when to prefer it over inspecting reservations via dhcp_reservations first, or whether removal is required in any scenario.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.