Skip to main content
Glama

ip_mac_binding

Destructive

Manage IP-MAC (ARP) bindings on a TP-Link router: view status, enable or disable binding, add, update, remove entries, or bind a current ARP entry by MAC or IP.

Instructions

IP-MAC binding (ARP binding): action=status|list (setting, bindings, live ARP table) | enable | disable | add (mac, ip, name, description) | update (mac + ip/name/description/enable; done as remove+re-add) | remove (mac) | bind_current (bind an ARP entry as-is, by mac or ip). Binding THIS machine to a different IP is CRITICAL.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "ip_mac_binding"
  }
}

Input Schema

NameRequiredDescriptionDefault
ipNo
macNo
nameNo
applyNofalse (default) = dry run: show the plan, diff, warnings and risk, send nothing. true = send it.
actionNostatus
enableNo
revealNoShow secrets (passwords/keys) unmasked.
routerNoWhich router (see router_status 'routers'); default main.main
descriptionNo
confirm_tokenNoRequired with apply=true for CRITICAL changes: the token from the dry run (valid 5 minutes, bound to the exact plan and current router state).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare a destructive, non-idempotent write, and the description adds real behavior beyond that: 'update' is implemented as remove+re-add (implying a transient unbound window), and it flags the CRITICAL risk of binding this machine to a different IP. It stops short of describing the dry-run/confirm-token safety flow, though that is documented in the schema.

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?

A single front-loaded sentence with a pipe-delimited action breakdown; dense but information-bearing, with the critical warning placed last for emphasis. The telegraphic style is slightly cryptic but wastes no words.

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 10-parameter destructive mutation tool with no output schema, the description covers action semantics, action-parameter mapping, the non-atomic update behavior, and the key risk. Remaining gaps (what list/status returns, permission requirements) are modest given the schema already documents dry-run and confirm_token.

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?

With only 40% schema description coverage across 10 parameters, the description compensates well by mapping parameters to actions — mac/ip/name/description for add, mac plus optional fields for update, mac for remove, mac-or-ip for bind_current. It does not clarify optional-vs-required per action beyond that mapping.

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 names the resource precisely ('IP-MAC binding (ARP binding)') and enumerates what each action does, so an agent knows it manages static ARP bindings rather than general router config. It does not explicitly contrast itself with sibling write tools like router_raw_write, keeping it short of 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?

Usage is implied through a per-action breakdown (status/list for inspection, add/update/remove for mutation, bind_current to promote an existing ARP entry), which is genuinely helpful routing between actions. However, there is no guidance on when to prefer this over a raw-write sibling, no prerequisites, and no explicit when-not conditions.

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