Skip to main content
Glama

extender

Read-onlyIdempotent

Inspect and manage TP-Link RE-series range extension settings, including status, uplink, extended/guest networks, clients, mesh, Wi-Fi, system, and logs; reveal credentials only when requested.

Instructions

TP-Link range extender (RE series). action=status (model, mode, uplink signal, mesh role) | uplink (the network it connects to) | extended (networks it broadcasts) | guest | mesh | network | clients | wifi_advanced | system (mode, time, LEDs, eco, power schedule) | logs. Secrets masked unless reveal.

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

Input Schema

NameRequiredDescriptionDefault
actionNostatus
revealNoShow secrets (passwords/keys) unmasked.
routerNoWhich router (see router_status 'routers'); default main.main

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 readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered structurally. The description still adds real behavioral context with 'Secrets masked unless reveal', telling the agent the default output hides passwords/keys and how to unmask them — a detail not derivable from 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 compact pipe-delimited block that front-loads the device identity and then the action map; no filler sentences. Slightly dense and the parenthetical glosses are applied inconsistently, but nothing is wasted.

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 read-only section-dispatch tool with no output schema, the description covers the dispatch parameter well and notes the secrets-masking behavior. It does not describe return shape for the unexplained actions, but with annotations carrying the safety profile this is close to complete.

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?

The schema only enumerates action values with no per-value descriptions, and the description compensates by explaining what each value targets (uplink = the network it connects to, extended = networks it broadcasts, system = mode/time/LEDs/eco/power schedule). reveal and router are already documented in the schema, so the remaining gap is the unannotated actions like guest, mesh, clients, and logs.

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 opens with the exact device class ('TP-Link range extender (RE series)') and enumerates the read sections it exposes via action, so an agent knows this is the read side of the extender surface. It never explicitly names the write counterpart extender_set, so the sibling split is inferable rather than stated.

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 action list implicitly tells the agent which section to request, and the default 'status' is the natural entry point, but there is no guidance on when to prefer this over router_status, clients, or mesh, nor an explicit warning to use extender_set instead for changes.

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