hdhomerun_run_doctorRun all diagnostic checks on your HDHomeRun setup and get a single aggregate report to identify configuration or signal issues.
Run every check and return the aggregate report.
| Name | Required | Description | Default |
|---|---|---|---|
| jellyfin_url | No | ||
| signal_channels | No | ||
| jellyfin_api_key | No | ||
| validate_device_auth_cloud | No |
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v1.3.6Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations flag openWorldHint=true, readOnlyHint=false, destructiveHint=false, but the description adds nothing about network/cloud contact, runtime cost, or side effects of the auth-validation flag. For a tool that can reach external services, this leaves important behavior undisclosed.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
A single front-loaded sentence with no waste, but the brevity comes at the cost of substance rather than delivering efficient information.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
An output schema exists, so return values needn't be explained, but with four undocumented optional parameters and no statement of which checks run or what enabling the Jellyfin/cloud inputs changes, the description is not sufficient for correct invocation.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0% for four parameters, and the description explains none of them — not jellyfin_url, jellyfin_api_key, signal_channels, nor validate_device_auth_cloud. An agent must guess that these are optional inputs affecting the checks performed.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a verb ('Run') and a resource in the sense of a diagnostic suite ('every check'), plus the aggregate report output. However, 'every check' is never enumerated and the numerous hdhomerun_check_* siblings are not referenced, so an agent cannot tell exactly what this covers without reading the schema.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance on when to use this versus the granular checks (hdhomerun_check_device_reachable, hdhomerun_check_signal_strength, hdhomerun_check_tuner_count_vs_jellyfin, etc.). There is also no note on whether the optional Jellyfin parameters are required for full coverage.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.