Skip to main content
Glama
Sign In
radarr-mcp

radarr-mcp

by arr-mcps
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

radarr_get_config_host

Read-only

List the Radarr host configuration, including hostname, port, and URL base, to verify server settings and troubleshoot connection errors.

Instructions

List host.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.3/5.0
Behavior2/5

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

The readOnlyHint annotation indicates a read-only operation, and the description's 'List' is consistent. However, the description adds no behavioral details beyond the annotation—it doesn't state what the returned data contains, whether it returns a single object, or any prerequisites.

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

Conciseness2/5

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

Two words is not conciseness; it's under-specification. It omits essential context about what 'host' means and what the tool returns. The description fails to earn its place because it provides almost no information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Even though an output schema exists, the description lacks any context about the host configuration domain. It doesn't clarify whether this returns the current host settings or a list of hosts. For a simple getter, it needs at least a few words to specify the resource.

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 has zero parameters, so there is nothing to explain. The description adds no input semantics, but none are needed. Baseline for zero-param tools is 4.

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

Purpose2/5

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

The description 'List host' is extremely vague. It doesn't specify that this retrieves host configuration settings, nor does it clarify the difference from sibling tools like get_config_host_by_id. The verb 'list' suggests enumerating multiple hosts, which is likely incorrect.

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 is provided on when to use this tool. There is no mention of alternatives or exclusion criteria. The description offers no context for selecting this over other config getters.

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