Skip to main content
Glama

Movies

by io.github.pipeworx-io

Get Tv Show

get_tv_show
Read-onlyIdempotent

Full TVmaze record for ONE TV series by its numeric TVmaze show id — the episode list with air dates, plus network, status and rating. The id is an internal TVmaze number, so resolve it with search_tv_shows first and pass what that returns; when the caller names the show rather than an id, search_tv_shows answers directly.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesTVmaze show ID (e.g., 1 for "Under the Dome")

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesTVmaze show ID
urlYesTVmaze show URL
nameYesShow name
typeYesShow type
endedYesEnd date
imageYesPoster image URL
genresYesList of genres
ratingYesAverage rating
statusYesCurrent status
networkYesNetwork name
summaryYesShow summary
episodesYes
languageYesPrimary language
premieredYesPremiere date
episode_countYesTotal number of episodes

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": {
+    "ended": {
+      "description": "End date",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "episode_count": {
+      "description": "Total number of episodes",
+      "type": "number"
+    },
+    "episodes": {
+      "items": {
+        "properties": {
+          "airdate": {
+            "description": "Air date in YYYY-MM-DD format",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "airtime": {
+            "description": "Air time (HH:MM format)",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "episode": {
+            "description": "Episode number in season",
+            "type": [
+              "number",
+              "null"
+            ]
+          },
+          "id": {
+            "description": "Episode ID",
+            "type": "number"
+          },
+          "name": {
+            "description": "Episode name",
+            "type": "string"
+          },
+          "runtime_minutes": {
+            "description": "Episode runtime in minutes",
+            "type": [
+              "number",
+              "null"
+            ]
+          },
+          "season": {
+            "description": "Season number",
+            "type": "number"
+          },
+          "summary": {
+            "description": "Episode summary without HTML",
+            "type": [
+              "string",
+              "null"
+            ]
+          }
+        },
+        "required": [
+          "id",
+          "season",
+          "episode",
+          "name",
+          "airdate",
+          "airtime",
+          "runtime_minutes",
+          "summary"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "genres": {
+      "description": "List of genres",
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "id": {
+      "description": "TVmaze show ID",
+      "type": "number"
+    },
+    "image": {
+      "description": "Poster image URL",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "language": {
+      "description": "Primary language",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "name": {
+      "description": "Show name",
+      "type": "string"
+    },
+    "network": {
+      "description": "Network name",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "premiered": {
+      "description": "Premiere date",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "rating": {
+      "description": "Average rating",
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "status": {
+      "description": "Current status",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "summary": {
+      "description": "Show summary",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "type": {
+      "description": "Show type",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "url": {
+      "description": "TVmaze show URL",
+      "type": [
+        "string",
+        "null"
+      ]
+    }
+  },
+  "required": [
+    "id",
+    "name",
+    "type",
+    "language",
+    "genres",
+    "status",
+    "premiered",
+    "ended",
+    "rating",
+    "network",
+    "summary",
+    "url",
+    "image",
+    "episode_count",
+    "episodes"
+  ],
+  "type": "object"
+}
  2. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "id": 1
+  },
+  {
+    "id": 169
+  }
+]
  3. First observed

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already provide readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false. The description adds value by specifying that the tool returns a single record (not a list) and lists the content (episodes, network, status, rating). This contextualizes the openWorldHint by giving typical fields, though it does not detail edge cases or error behaviors.

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?

Two sentences, front-loaded with the primary purpose, and each sentence serves a distinct role: first states what the tool does, second explains when and how to use it. No filler or redundant content.

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?

Given the low complexity (one required parameter, no enums, output schema present), the description covers all necessary aspects: purpose, input semantics, output content, usage context, and sibling differentiation. The output schema handles return structure, so no further detail needed.

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 coverage is 100% with a good example and description for the 'id' parameter. The description adds extra meaning by clarifying that the id is an internal TVmaze number and that it must be resolved via 'search_tv_shows', which goes beyond the schema's static example.

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 it returns the full TVmaze record for one TV series by its numeric ID, including episode list, air dates, network, status, and rating. It uses specific verbs ('full record') and resources ('TV series') and distinguishes itself from sibling 'search_tv_shows' by focusing on a single existing ID.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly tells when to use this tool (when the caller has a numeric TVmaze ID) and when not (when the caller names the show, use 'search_tv_shows' instead). It also explains the prerequisite of resolving the ID via 'search_tv_shows' first, leaving no ambiguity about the workflow.

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