Skip to main content
Glama
Sign In
fritz-mesh-mcp

fritz-mesh-mcp

by gr9driver
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

fritz_set_guest_wifi

Enable or disable the guest Wi-Fi network on the FRITZ!Box master to control temporary visitor access without changing the main Wi-Fi.

Instructions

Enable or disable the guest Wi-Fi network on the master.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "enabled": "<enabled>"
    },
    "name": "fritz_set_guest_wifi"
  }
}

Input Schema

NameRequiredDescriptionDefault
enabledYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden, yet it says nothing about side effects (connected guest clients being dropped on disable), whether the change persists across reboots, permissions/auth needed, or error behavior. The only behavioral hint is the 'on the master' scope.

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?

A single short sentence with zero filler, front-loaded with the action and the target. Nothing to trim.

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 one-boolean, no-output-schema mutation tool the description is minimally sufficient to call it, but with no annotations it leaves the agent guessing about side effects and preconditions that matter for a network-disrupting toggle.

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?

There is one parameter with 0% schema description coverage, but the phrase 'Enable or disable' maps directly onto the boolean 'enabled', making its meaning inferable. No default, no note on what happens if the guest network is already in the requested state.

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 pair (enable/disable) and a specific resource (guest Wi-Fi network on the master), so the agent knows exactly what state it changes. It does not explicitly contrast with siblings such as fritz_wifi_networks, but the guest-Wi-Fi scope is unambiguous.

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 only implied by the verb: call it to toggle guest Wi-Fi. There is no statement of prerequisites (guest Wi-Fi must be configured on the master) or of the read-only alternative (fritz_wifi_networks) for checking current state before changing it.

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

Deploy Server

Other Tools