Skip to main content
Glama
Sign In
stremio-mcp

stremio-mcp

by netixc
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

play

Play movies or TV shows by searching title or using IMDb ID. Supports season, episode, and year filters for precise playback.

Instructions

Play movies or TV episodes. Use 'query' to search by title, or 'imdb_id' to play directly.

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

Input Schema

NameRequiredDescriptionDefault
typeNomovie or tv (required with query)
yearNoOptional year filter
queryNoTitle to search and play
seasonNoSeason number (for TV)
sourceNosearch (TMDB) or library (Stremio)search
episodeNoEpisode number (for TV)
imdb_idNoIMDb ID (e.g., tt0111161)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior3/5

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

No annotations provided, so description must disclose behavior. It states it 'plays' content but omits side effects (e.g., starting playback, handling multiple results, authentication requirements). Adequate but not comprehensive.

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

Conciseness5/5

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

Two sentences, front-loaded with purpose, then usage guidance. No filler.

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 7 parameters (none required) and no output schema, the description covers only the two primary modes. Does not explain parameters like year, season, episode, or source in context, nor describe expected output or errors.

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?

Schema coverage is 100%; description adds value by explaining the two main invocation modes (query vs imdb_id) and their relationship, going beyond individual parameter descriptions.

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

Purpose5/5

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

Clearly states verb ('play') and resource ('movies or TV episodes'), and distinguishes from sibling tools like 'search' and 'library' by implying play action.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides explicit use cases: search by title or use IMDb ID. Lacks explicit when-not-to-use or comparison with siblings, but offers clear guidance on invocation methods.

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