Skip to main content
Glama

fs_series_detail

Retrieve detailed information for a German TV series from fernsehserien.de using a slug or series URL, including description, seasons, episode-guide links, air dates, and streams.

Instructions

Series details: description, seasons and links to the episode guide, air dates and streams. series: a slug (babylon-berlin) or a fernsehserien.de series URL.

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_series_detail"
  }
}

Input Schema

NameRequiredDescriptionDefault
seriesYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It discloses the kind of data returned, but does not discuss read-only safety, authentication, rate limits, error behavior, or whether URL and slug inputs behave differently.

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?

The description is short, front-loaded, and free of filler. It first states the returned details, then clarifies the accepted parameter format.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple one-parameter lookup with an output schema, the description is largely complete: it documents the input formats and summarizes returned content. The main gap is the absence of explicit sibling-routing guidance.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The single parameter has 0% schema description coverage, so the description must compensate, and it does: it explains that `series` accepts either a slug like babylon-berlin or a fernsehserien.de series URL. This adds critical meaning beyond the bare schema.

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 identifies the resource and what is returned: series description, seasons, episode guide links, air dates, and streams. It does not explicitly distinguish the tool from siblings such as fs_air_dates or fs_episodes, but the purpose is readily understandable.

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?

Usage is implied: this is the detail lookup for a specific series. The description does not say when to use it instead of fs_search_series, fs_air_dates, or fs_episodes, nor does it provide exclusions or prerequisites.

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