Skip to main content
Glama

fs_episodes

Retrieve episode numbers, titles, runtimes, and airing details for any season of a German TV series by providing its slug or URL. Set season and limit to focus the guide.

Instructions

Episode guide for one season: episode number, title, runtime and airings (type, date, channel). series: a slug or URL. season: the season number (default 1). limit: 1..20 (default 10).

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": "<series>"
    },
    "name": "fs_episodes"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
seasonNo
seriesYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the whole burden. It does disclose the fields returned (episode number, title, runtime, airings with type/date/channel) and the parameter limits and defaults, which helps. It says nothing about ordering, error behavior for a bad series or season, or any access/rate-limit constraints.

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?

Very compact and front-loaded: the returned fields come first, then each parameter in order. Nothing is wasted, though the telegraphic style and split lines make it slightly less readable than a clean sentence structure would be.

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?

An output schema exists, so return-value explanation is not strictly required, and the description still summarizes it usefully. For a three-parameter read tool this is close to complete, but with zero annotation coverage it leaves ordering and failure behavior unstated.

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 description coverage is 0%, so the description has to do the work and it largely does: series is a slug or URL, season is the season number defaulting to 1, and limit is bounded 1..20 with default 10. That bound is not encoded in the schema, so the description genuinely adds meaning. Minor gap: 'series' accepts two forms but the accepted URL shape is not shown.

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?

States a concrete resource and scope: an episode guide for one season, listing episode number, title, runtime and airings. That is far more specific than the bare name 'fs_episodes'. It does not distinguish itself from siblings like fs_air_dates or fs_series_detail, so it stops short of a 5.

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?

There is no explicit when-to-use statement, no prerequisites, and no mention of alternatives such as fs_air_dates or fs_series_detail. The only guidance is implicit: you pass a series slug or URL plus a season number to get that season's episodes.

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