Retrieve quality profiles, root folders, tags, and Sonarr language profiles from a selected Radarr or Sonarr server to set up media requests correctly.
Get quality profiles, root folders, tags, and language profiles (Sonarr) for a Radarr/Sonarr server.
| Name | Required | Description | Default |
|---|---|---|---|
| serverId | No | Server ID from get_services (default: 0) | |
| serviceType | Yes | Service type |
Changes observed during successful MCP inspections.
v2.3.1Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided, so description carries full burden. It states it retrieves data but does not disclose auth requirements, side effects, rate limits, or whether the tool is read-only (implied but not explicit).
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?
One sentence, front-loaded with key purpose, no fluff. Every word earns its place.
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?
Given simple parameters and no output schema, description adequately lists the types of data returned. Could mention that servers from get_services are needed, but it's implied. Minor gap for moderate completeness.
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 coverage is 100% (both parameters described). The description adds no extra meaning beyond the schema; it lists output types but not parameter details. Baseline 3 is appropriate.
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?
The description clearly states the verb 'Get' and the resources: quality profiles, root folders, tags, and language profiles for a Radarr/Sonarr server. It distinguishes from siblings like get_media_details (media items) and get_services (list servers).
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 tool vs siblings like get_media_details or search_media. No mention of prerequisites, when not to use, or how it fits in a workflow.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.