Skip to main content
Glama

fs_air_dates

Retrieve upcoming air dates for a German TV series, including start/end times, channel, episode code and title; set a limit to plan viewing.

Instructions

Upcoming air dates (Sendetermine) for a series: start/end, channel, episode code and title. series: a slug or URL. 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_air_dates"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
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 full burden. It does disclose the key behavioral trait — that results are filtered to upcoming dates and include start/end plus channel and episode code — but says nothing about ordering, window size, what happens with an unknown series, or pagination beyond the limit.

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?

Two compact clauses: the purpose and return fields first, then parameter notes. No filler, though the telegraphic phrasing ("start/end, channel, episode code and title") borders on terse for an unfamiliar reader.

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?

With only two parameters and an output schema present, the description need not restate return values, and it covers both inputs. What is missing is routing guidance among the overlapping sibling tools and any note on result ordering, which leaves an agent guessing in a crowded namespace.

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 must compensate, and it largely does: it explains that series accepts a slug or URL and that limit is bounded 1..20 with a default of 10. The only gap is the upstream schema's own default of 10, which happens to be consistent here.

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?

"Upcoming air dates (Sendetermine) for a series" states a specific verb-like resource and scopes it to future dates, with the returned fields (start/end, channel, episode code, title) listed. It does not explicitly distinguish itself from the sibling fs_episodes, which plausibly covers similar episode data, so sibling differentiation is left to inference.

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 says nothing about when to pick this over fs_episodes, fs_series_detail, or fs_search_series, nor any prerequisite such as needing a valid series identifier first. Usage is only implied by the word "upcoming".

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