Skip to main content
Glama

tvmaze-mcp-server

Tvmaze Get Schedule

tvmaze_get_schedule
Read-onlyIdempotent

List television episodes airing on a given date. Scope "linear" covers broadcast and cable networks in one country; "streaming" covers streaming services — global services such as Netflix and Prime Video when no country is given, or that country’s local streaming services when one is. Scope "all" merges both. The source caches schedule data for up to an hour, so a same-day listing can lag a late change.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dateNoDate to list, ISO 8601 (YYYY-MM-DD). Defaults to today in the requested timezone.
limitNoMaximum entries to return in one call. A full day in one country runs to roughly 50 broadcast entries and over 120 global streaming entries.
scopeNoWhich feed to read. "linear" is broadcast and cable networks; "streaming" is streaming services; "all" merges both and costs three upstream requests.linear
cursorNoContinuation token from a previous call’s next_cursor. Omit for the first page.
countryNoISO 3166-1 alpha-2 country code, e.g. "US", "GB", "JP". The United Kingdom is "GB". Required in effect for scopes "linear" and "all" — omitted, it falls back to the server-configured country. For scope "streaming", omitting it selects global streaming services rather than one country’s local ones.
timezoneNoIANA timezone name for the air times, e.g. "America/Los_Angeles". Defaults to the server-configured timezone. Also decides what "today" means when date is omitted.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
capNoThe page limit that was applied.
dateNoDate listed, ISO 8601 (YYYY-MM-DD).
errorNoPresent when the call failed. Absent on success.
shownNoNumber of entries returned on this page.
noticeNoGuidance when nothing is listed, or when one feed of a merged query did not respond. Absent otherwise.
entriesNoEpisodes airing on the date, earliest first.
has_moreNoTrue when more entries remain beyond this page.
timezoneNoIANA timezone the air times were rendered in.
truncatedNoTrue when the page limit was reached.
totalCountNoMerged entry count before the page limit was applied.
next_cursorNoPass as cursor to fetch the next page. Absent on the last page.
applied_feedsNoExactly which upstream feeds the results cover, e.g. ["linear:US"], ["web:global"], ["linear:GB","web:GB","web:global"].

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the readOnly/idempotent/openWorld annotations, the description discloses meaningful behavioral details: schedule data is cached for up to an hour and may lag late changes, and the "all" scope costs three upstream requests. This helps an agent anticipate staleness and cost without contradicting the annotations.

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?

Four sentences, front-loaded with the core action, and each sentence earns its place. The scope definitions are compact, and the caching caveat is a single clear warning. No filler or redundant restating of the schema.

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

Completeness5/5

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

The description is complete for this tool: it addresses the main decision axes (scope, country, timezone), discloses the cache and request-cost behavior, and relies on the output schema and detailed parameter schema for paging and return values. Nothing essential is missing.

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 schema already covers all six parameters with 100% coverage, so the baseline is 3. The description adds value by integrating parameter meanings into scenarios: how scope and country interact for streaming services, what "all" costs, and how timezone affects the default date. This is useful beyond the isolated schema 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?

The description opens with a specific verb and resource: "List television episodes airing on a given date." It then clarifies the three scope variants, which clearly differentiates this from show/cast/episode lookup siblings. An agent can immediately know what this tool does and how it differs from related tools.

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?

The description gives clear context for choosing between linear, streaming, and all scopes, and explains how country affects global vs local streaming. It does not explicitly name sibling alternatives or say when not to use this tool, but the schedule-specific purpose and scope guidance are sufficient for correct selection.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.