Skip to main content
Glama

ddns

Destructive

Manage Dynamic DNS on TP-Link routers: check status, refresh provider, add/remove/bind domains, and log in to No-IP or DynDNS. Use dry runs and confirm tokens for safe changes.

Instructions

Dynamic DNS. action=status | refresh (provider) | tplink: add / remove / bind / unbind (domain) | noip / dyndns: login (username, domain, password_file[, wan_bind]) | logout.

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

Input Schema

NameRequiredDescriptionDefault
applyNofalse (default) = dry run: show the plan, diff, warnings and risk, send nothing. true = send it.
actionNostatus
domainNo
revealNoShow secrets (passwords/keys) unmasked.
routerNoWhich router (see router_status 'routers'); default main.main
providerNo
usernameNo
wan_bindNo
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).
password_fileNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, openWorldHint=false, and non-idempotent, so the safety profile is partly covered. The description adds provider/action compatibility, but says nothing about the dry-run-first model, the confirm_token requirement for critical changes, or what remove/unbind actually destroys — all of which the agent must discover from the schema's `apply` and `confirm_token` field descriptions. No contradiction with annotations.

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 no filler; every clause carries action-to-parameter information. The highly compressed pipe/parenthesis notation costs some readability and arguably overshoots conciseness into under-specification.

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 destructive, 10-parameter tool with no output schema, the action routing is present but the operational contract is not: the dry-run default, the five-minute confirm_token flow for critical changes, and what a status or refresh call returns are left entirely to the schema. An agent can pick an action but must read the schema to execute it safely.

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: it binds domain to the tplink actions, username/domain/password_file/wan_bind to the noip/dyndns login action, and provider to refresh, telling the agent which parameters matter for which action. It leaves apply, reveal, router, and confirm_token to their schema descriptions, and does not explain formats (e.g. what password_file points to).

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 (Dynamic DNS) and enumerates the concrete operations (status, refresh, add/remove/bind/unbind, login, logout), which is enough for an agent to recognize this as the DDNS management tool rather than internet, routing, or vpn_server. The compressed 'provider: action' notation is terse but decodable. It stops short of a plain-language statement of scope, so it lands at 4 rather than 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?

It effectively encodes which action applies to which provider — refresh takes a provider, tplink uses add/remove/bind/unbind with a domain, noip/dyndns use login with username/domain/password_file and optional wan_bind — which is real routing guidance between action variants. It gives no guidance on when to choose this tool over siblings, no when-not conditions, and no note on when status versus refresh should be used.

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