tplink-mcp

Overview Schema Source Related Servers Discussions Admin

set_dhcp_settings

Update selected DHCP server settings on a TP-Link router, including enable state, gateway, DNS, IP range, and lease time. Restarts DHCP; existing leases retain their IP until renewal.

Instructions

Update DHCP server settings (only the given fields). Restarts the DHCP server; existing leases keep their IP until renewal. leasetime is in minutes.

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": "set_dhcp_settings"
  }
}

Input Schema

Name	Required	Description	Default
`enable`	No
`gateway`	No
`pri_dns`	No
`snd_dns`	No
`leasetime`	No
`ipaddr_end`	No
`ipaddr_start`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 26, 2026

TDQS

A3.7/5.0

Behavior4/5

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

With no annotations, the description carries the full behavioral burden and does disclose the most important traits: the DHCP server restarts, existing leases retain their IP until renewal, and leasetime is in minutes. Missing is guidance on permission/auth requirements, whether a bad range is rejected, and the risk of misconfiguring gateway/DNS for all clients.

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 with no waste; the partial-update constraint comes first, followed by the side effects. Every clause earns its place.

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

Completeness3/5

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

For a 7-parameter mutation tool with a restart side effect, no annotations, and no output schema, the description covers the critical operational behavior but leaves out risk guidance (e.g., disabling DHCP or an invalid address range cutting off clients) and what the call returns.

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% across 7 params, so the description must compensate. It adds the unit for leasetime (minutes) and, via 'only the given fields', explains that null/unset parameters leave existing values untouched – but it says nothing about the enable flag, the gateway/DNS fields, or the relationship between ipaddr_start and ipaddr_end.

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 ('Update DHCP server settings') and immediately clarifies the partial-update semantics with 'only the given fields'. It is distinct from the read-side siblings (get_dhcp_settings, dhcp_leases) without naming them, so an agent can differentiate but must infer.

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 'only the given fields' clause implies partial-update usage and how to combine with get_dhcp_settings, but no explicit when-to-use or when-not-to-use guidance is given. Nothing warns about prerequisites such as reading current settings first or validating that ipaddr_start precedes ipaddr_end.

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