Skip to main content
Glama

get_calendar_episodes

Retrieve upcoming TV show episodes from MyShows calendar to track air dates and episode details for viewing planning.

Instructions

Retrieves the calendar episodes from MyShows with information about the next episodes. This method fetches the next episodes scheduled to air, including their details. :return: A dictionary containing the calendar episodes.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • MCP tool handler for 'get_calendar_episodes'. Decorated with @mcp.tool() for registration and @tool_handler for error handling. Delegates execution to the MyShowsAPI client.
    @mcp.tool()
    @tool_handler
    async def get_calendar_episodes():
        """Retrieves the calendar episodes from MyShows with information about the next episodes.
        This method fetches the next episodes scheduled to air, including their details.
        :return: A dictionary containing the calendar episodes.
        """
        return await api_client.get_calendar_episodes()
  • Core implementation of get_calendar_episodes in MyShowsAPI class. Makes a JSON-RPC call to 'lists.Episodes' with params {"list": "next"} to fetch upcoming episodes.
    async def get_calendar_episodes(self) -> Dict[str, Any]:
        """Retrieves the calendar episodes from MyShows with information about the next episodes.
        This method fetches the next episodes scheduled to air, including their details.
        :return: A dictionary containing the calendar episodes.
        """
        return await self._make_request(
            method="lists.Episodes", id=86, params={"list": "next"}
        )
Behavior2/5

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

No annotations are provided, so the description carries full burden for behavioral disclosure. It states the tool retrieves/fetches data, implying a read-only operation, but doesn't specify authentication needs, rate limits, error handling, or data freshness. The mention of 'next episodes scheduled to air' hints at future-oriented data, but behavioral traits like pagination or response format are not described.

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

Conciseness3/5

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

The description is reasonably concise with three sentences, but has some redundancy: 'Retrieves the calendar episodes' and 'This method fetches the next episodes' convey similar information. The return statement adds value by specifying output format. However, it could be more front-loaded by merging the first two sentences for better flow.

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?

Given the tool's simplicity (0 parameters, no output schema, no annotations), the description is minimally adequate. It explains what the tool does and the return format, but lacks behavioral context like authentication or error handling. For a read operation with no complex inputs, this is acceptable but leaves gaps an agent might need to infer.

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 input schema has 0 parameters with 100% coverage, so no parameter documentation is needed. The description appropriately doesn't discuss parameters, maintaining focus on the tool's purpose. This meets the baseline for tools with no parameters.

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?

The description clearly states the tool's purpose: retrieving calendar episodes from MyShows with information about next episodes. It specifies the resource (calendar episodes from MyShows) and action (retrieves/fetches next episodes scheduled to air). However, it doesn't explicitly differentiate from sibling tools like 'get_viewed_episodes' or 'check_episode' which might also involve episode data.

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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention any prerequisites, context for use, or comparison to sibling tools like 'get_myshows_profile_shows_list' or 'search_shows' that might retrieve similar data. The agent must infer usage from the purpose alone.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/zeloras/myshows_mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server