Skip to main content
Glama

lidarr_get_calendar

Read-only

Retrieves upcoming album releases from Lidarr within a specified number of days, defaulting to 30.

Instructions

Get upcoming album releases from Lidarr

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

Input Schema

NameRequiredDescriptionDefault
daysNoNumber of days to look ahead (default: 30)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description's only added behavioral signal is that results are limited to upcoming (future) releases; it says nothing about ordering, result size, or how the lookahead window is applied beyond what the schema shows.

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?

One short, front-loaded sentence with no filler. It is efficient, though the brevity leaves little room for the scoping detail an agent might want.

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?

For a simple read-only lookahead tool with one documented optional parameter and no output schema, the description covers the essentials. It still omits the default lookahead behavior and any distinction from catalog-listing tools, which would round it out.

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 description coverage is 100% and the single optional param carries its own description including a default of 30 days, so the schema does the work. The description adds no further meaning about how the day window is interpreted (calendar days vs release dates).

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?

"Get upcoming album releases from Lidarr" names a specific verb (get) and resource (upcoming album releases), which is enough for an agent to distinguish it from catalog tools such as lidarr_get_albums. It never explicitly references those siblings, so it falls short of the top mark.

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?

The word "upcoming" implies the tool is for looking ahead at future releases rather than browsing the library, but there is no explicit when-to-use or when-not-to-use guidance and no named alternative (e.g., lidarr_get_albums for existing albums).

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