fritz-mesh-mcp

by gr9driver

Overview Schema Source Related Servers Discussions Admin

Python

Local

fritz_smart_home_devices

Retrieve the DECT smart-home devices visible to the FRITZ!Box master to inspect connected switches and sensors.

Instructions

DECT smart-home devices the master can see.

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

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 2, 2026

TDQS

C2.8/5.0

Behavior2/5

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

With no annotations, the description carries the full disclosure burden and delivers almost none: read-only-ness is only implied, and there is no mention of whether results are cached, how large the DECT device set may be, or what 'the master' implies about permissions. The phrase 'the master can see' is the sole behavioral hint and is unexplained.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One short sentence with no padding, so nothing is wasted, but the terseness crosses into under-specification and the sentence is a bare noun phrase rather than a statement of action.

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?

This is a simple zero-parameter read tool with an output schema, so return-value detail is not needed, and the description covers the basic scope. It still omits the read-only framing and any sense of what the DECT device entries represent, which an agent would want before calling.

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 tool takes zero parameters, so there is nothing for the description to disambiguate and the schema is trivially complete. Baseline 4 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The fragment 'DECT smart-home devices' identifies the resource and narrows scope versus the generic fritz_list_devices, but the sentence has no verb and never says it returns a list. An agent can guess the intent from the name plus 'DECT', yet the purpose is only implied, not stated.

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

Usage Guidelines2/5

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

No guidance on when to call this versus fritz_list_devices or fritz_get_device, and no prerequisites or exclusions are mentioned. The 'master can see' clause hints at scope but does not route the agent between siblings.

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