Skip to main content
Glama

set_static_ip

Destructive

Assign or update a device's fixed IP address reservation by MAC address, previewing the change before applying it so the device receives the address on lease renewal.

Instructions

Give a device a fixed IP (address reservation): adds it, or updates the existing reservation for that MAC. The device gets the address the next time it renews its lease. 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>",
      "ip": "<ip>"
    },
    "name": "set_static_ip"
  }
}

Input Schema

NameRequiredDescriptionDefault
ipYes
macYes
confirmNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations flag destructiveHint=true and readOnlyHint=false, and the description adds real context beyond that: the destructive part is replacing an existing reservation for the same MAC, and the change is deferred until lease renewal rather than immediate. It also discloses the dry-run default. Gaps remain around authorization, conflicting/reserved IPs, and behavior for an unknown MAC.

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, both earning their place, with the upsert scope stated first and the lease-timing and confirm semantics following. No filler or restatement of the tool name.

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 three-parameter mutation tool with no output schema, the description covers what changes, when it takes effect, and how to preview it safely. It stops short of describing failure conditions or the shape of the returned reservation/preview, which an agent may still need.

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

Parameters4/5

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

Schema coverage is 0%, so the description must carry the load, and it does for all three parameters: mac keys the reservation, ip is the address being reserved, and confirm gates preview versus apply. Only the address format and validation rules for ip are left unstated.

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

Purpose5/5

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

The description gives a specific verb and resource ('Give a device a fixed IP (address reservation)') and immediately defines the operation as an upsert ('adds it, or updates the existing reservation for that MAC'). That wording also implicitly separates it from remove_static_ip and from read-only siblings like dhcp_reservations.

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

Usage Guidelines4/5

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

It clearly states the two operating modes and which argument selects them: 'Without confirm=true it only shows the plan,' implying confirm=true applies the change. It does not point at alternatives such as checking dhcp_reservations or find_client first, but the in-tool guidance is unambiguous.

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