Skip to main content
Glama

access_control

Destructive

Manage which devices may use a TP-Link router network: view status and candidates, allow or block devices by MAC, and switch black/white access modes with dry-run safety.

Instructions

Access control (who may use the network). action=status | candidates | enable | disable | set_mode (mode=black|white) | block / unblock (mac[, name]) | allow / disallow (mac). Black mode blocks listed devices; white mode blocks everything NOT listed. Switching to white mode, enabling it, or blocking THIS machine 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": "access_control"
  }
}

Input Schema

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

A4.7/5.0
Behavior5/5

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

Beyond the `destructiveHint: true` in the annotations, the description adds crucial behavioral context by defining the specific risk associated with certain actions. It explicitly warns that switching to white mode, enabling the tool, or blocking this specific machine is 'CRITICAL.'

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?

The definition is highly dense because it must cover the full functional scope and all mode behaviors in one unit. While long, its structure flows logically from general purpose to specific actions and then to crucial operational warnings.

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 complexity of providing different behaviors for eight distinct actions and two operational modes, the description is highly complete. It effectively manages expectations regarding the tool's scope and severity.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The description provides essential semantic meaning for the `action` and `mode` parameters, explaining exactly what Black and White modes achieve for device filtering. It links specific parameters like `mac` and `name` to the appropriate actions like 'block' or 'unblock.'

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 explicitly states the tool's purpose is 'access control' and lists all available high-level 'action' types (status, block, allow, etc.). It successfully distinguishes its function as network access management and outlines its distinct modes (black/white).

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

Usage Guidelines4/5

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

While it doesn't explicitly compare it against siblings, the detailed listing of actions (e.g., 'block' vs 'allow' vs 'set_mode') serves as robust functional guidance for the agent. The tool is clearly defined as a comprehensive control panel for network access policy.

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