Skip to main content
Glama
Sign In
Sonarr MCP Server

Sonarr MCP Server

by micky-devs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

get_series

Retrieve detailed information about a TV series in your Sonarr collection using its series ID.

Instructions

Get detailed information about a specific TV series

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": {
      "series_id": "<series_id>"
    },
    "name": "get_series"
  }
}

Input Schema

NameRequiredDescriptionDefault
series_idYesSonarr series ID (use the ID from list_series output)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior2/5

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

No annotations provided. Description only states 'get detailed information', lacking any disclosure of side effects, error handling, auth requirements, or rate limits. The read-only nature is 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.

Conciseness4/5

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

Single sentence of 8 words, no fluff. Front-loads purpose. Could benefit from slightly more detail, but no wasted text.

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?

Lacks explanation of what 'detailed information' includes, no output schema or example. For a simple retrieval tool with multiple siblings, more context needed to guide correct usage.

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?

Schema provides good description for series_id at 100% coverage. Description adds no extra meaning beyond what schema offers, so baseline 3.

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?

Clear verb 'Get' and resource 'detailed information about a specific TV series'. Differentiates from siblings like add/delete/update, but doesn't contrast with list_series which also retrieves series info.

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?

Schema suggests using ID from list_series, implying a retrieval context. No explicit when-to-use or when-not, and no mention of alternatives among siblings.

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