keenetic-mcp

pin_device

Idempotent

Turn a connected device's current IP into a static DHCP lease with one command, then save the config. Use this to assign a fixed IP without manual MAC lookup and avoid address conflicts.

Instructions

Turn a connected device's current IP into a static reservation in one step (no need to know the MAC), then save the config. Preferred way to give a device a fixed IP; use set_static_lease only for devices that are offline (not in list_devices). A name fragment must match exactly one device; an address-like identifier must be the full IP or MAC and never matches names ("66" won't hit "Room-66-Cam"). Passing ip moves the device there at its next lease renewal — get a candidate from find_free_ip. Refuses (changes nothing) if the target IP is active on or reserved to another device. Examples: pin_device("192.168.1.66") · pin_device("PS5", "192.168.1.154")

Input Schema

TableJSON Schema

Name	Required	Description	Default
`ip`	No	Optional IPv4 to pin to instead of the device's current IP. Empty = keep current IP.
`identifier`	Yes	Device IP (e.g. 192.168.1.66), MAC, or a fragment of its name, looked up in the active DHCP lease table.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedSep 23, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Beyond the annotations, the description discloses meaningful behavior: it saves the config, moves the device at next lease renewal, and refuses without changes if the target IP is active or reserved. It also explains identifier-matching quirks that could otherwise cause failures.

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 description is dense but every clause earns its place: scope, alternative routing, matching rules, side effects, conflict behavior, and examples. It is front-loaded with the core purpose and keeps examples compact.

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

Completeness5/5

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

Given the output schema and annotations, the description covers the prerequisites, alternatives, edge cases, parameter semantics, and failure behavior. An agent has enough information to select and invoke the tool correctly without additional inference.

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 100%, so the baseline is 3. The description adds valuable semantic detail beyond the schema: name fragments must match exactly one device, address-like identifiers never match names, and the ip parameter means 'move to this address at next renewal' with candidates from find_free_ip.

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 uses a specific verb and resource ('Turn a connected device's current IP into a static reservation') and explicitly contrasts the tool with set_static_lease. It is immediately clear what the tool does and how it differs from siblings.

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

Usage Guidelines5/5

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

The description gives explicit when-to-use guidance: pin_device is the preferred way for connected devices, set_static_lease is only for offline devices, and find_free_ip should supply candidate IPs. Examples further reinforce correct invocation.

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

Deploy Server