Skip to main content
Glama

Movies

by io.github.pipeworx-io

Get Tv Schedule

get_tv_schedule
Read-onlyIdempotent

Check what's broadcasting on a specific date and country (e.g., 'US', 'GB'). Returns shows, times, and channels.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dateNoDate in YYYY-MM-DD format (default: today)
countryNoISO 3166-1 alpha-2 country code (default "US")

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
dateYesSchedule date in YYYY-MM-DD format
countryYesISO 3166-1 alpha-2 country code
scheduleYes
total_airingsYesTotal number of airings on this date

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "country": {
+      "description": "ISO 3166-1 alpha-2 country code",
+      "type": "string"
+    },
+    "date": {
+      "description": "Schedule date in YYYY-MM-DD format",
+      "type": "string"
+    },
+    "schedule": {
+      "items": {
+        "properties": {
+          "airtime": {
+            "description": "Air time in HH:MM format",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "episode": {
+            "description": "Episode number in season",
+            "type": [
+              "number",
+              "null"
+            ]
+          },
+          "episode_name": {
+            "description": "Episode name",
+            "type": "string"
+          },
+          "network": {
+            "description": "Network or web channel name",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "runtime_minutes": {
+            "description": "Episode runtime in minutes",
+            "type": [
+              "number",
+              "null"
+            ]
+          },
+          "season": {
+            "description": "Season number",
+            "type": "number"
+          },
+          "show_name": {
+            "description": "Name of the show",
+            "type": [
+              "string",
+              "null"
+            ]
+          }
+        },
+        "required": [
+          "airtime",
+          "show_name",
+          "network",
+          "episode_name",
+          "season",
+          "episode",
+          "runtime_minutes"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "total_airings": {
+      "description": "Total number of airings on this date",
+      "type": "number"
+    }
+  },
+  "required": [
+    "country",
+    "date",
+    "total_airings",
+    "schedule"
+  ],
+  "type": "object"
+}
  2. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "country": "US"
+  },
+  {
+    "country": "GB",
+    "date": "2024-01-15"
+  }
+]
  3. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false, so the safety profile is clear. The description adds behavioral context by stating it 'Returns shows, times, and channels', which helps set expectations for output content beyond what annotations provide.

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 a single, well-structured sentence that immediately states the primary action, includes a clarifying example, and notes the return fields. No unnecessary words or repetition.

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?

For a simple read-only schedule tool, the description is complete. It covers purpose, key inputs, and output content. The presence of an output schema and fully documented parameters further reduces the burden on the description.

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

Parameters3/5

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

The input schema covers both parameters with descriptions and defaults (date format YYYY-MM-DD, country ISO code). The description adds little beyond confirming the use of date and country, so it does not significantly enhance parameter understanding.

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 clearly states the tool's function: 'Check what's broadcasting on a specific date and country'. It specifies the resource (TV schedule) and the key parameters (date, country), and differentiates from siblings like get_tv_show and search_tv_shows by focusing on broadcast schedule rather than show details or search.

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 provides clear context for when to use the tool (checking broadcasts by date and country) and gives examples of valid inputs. It does not explicitly name alternatives or exclusions, but the context is sufficient for a simple look-up tool in the presence of sibling tools.

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

All Movies toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.5/5.0
Disambiguation2/5

Many tools have heavily overlapping purposes—ask_pipeworx, ask_pipeworx_beta, and ask_pipeworx_grounded are nearly identical, while entity_profile, compare_entities, and recent_changes all pull overlapping company data. The server is named 'Movies' but only 4 of 35 tools relate to movies, making it impossible to infer what the tool set is actually for.

Naming Consistency2/5

Naming is a mix of verb_noun (search_movies, get_tv_schedule), bare nouns (remember, recall), brand prefixes (pipeworx_*, polymarket_*), and ad-hoc verbs (ask_pipeworx vs validate_claim). There is no consistent convention; even the pipeworx family uses ask_ vs grounded vs beta suffixes that don't follow a predictable pattern.

Tool Count2/5

35 tools is heavy for a single server, and for a 'Movies' server it is extreme overkill since the vast majority have nothing to do with movies. Even if the intent was a general data/betting server, 35 tools exceed the upper bound of the well-scoped range and would be better split into focused servers.

Completeness2/5

As a movies/TV server it is severely incomplete: there is no get_movie, no reviews, no watchlist, no person/actor search—only search_movies, search_tv_shows, get_tv_show, and get_tv_schedule. If instead the domain is Pipeworx data, coverage is better but still lacks mutation tools (e.g., no create/update for subscriptions beyond subscribe/unsubscribe) and the movie tools become dead weight.

Resources