Skip to main content
Glama

Tvmaze Lookup Show

tvmaze_lookup_show
Read-onlyIdempotent

Resolve a television show from its id in another catalog — IMDb, TheTVDB, or TVRage — and return the matching TVmaze profile. Use this to cross a show id from another source into TVmaze. A show absent from TVmaze is reported as a miss with guidance, not an error.

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
showNoThe resolved show. Absent on a miss.
errorNoPresent when the call failed. Absent on success.
foundNoTrue when the external id resolved to a TVmaze show.
sourceNoCatalog the lookup was made against.
guidanceNoWhat to do next when the lookup missed. Absent on a hit.
external_idNoId looked up; IMDb ids use the canonical lowercase tt prefix and original digits.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedOutput schema / properties / show / properties / network
      Added value: +{
      +  "additionalProperties": false,
      +  "description": "Broadcast or cable network, when recorded.",
      +  "properties": {
      +    "country": {
      +      "description": "ISO 3166-1 alpha-2 country of this carrier.",
      +      "type": "string"
      +    },
      +    "name": {
      +      "description": "Carrier name as TVmaze records it.",
      +      "type": "string"
      +    },
      +    "timezone": {
      +      "description": "IANA timezone recorded for this carrier.",
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "name"
      +  ],
      +  "type": "object"
      +}
    • addedOutput schema / properties / show / properties / web_channel
      Added value: +{
      +  "additionalProperties": false,
      +  "description": "Streaming service, when recorded.",
      +  "properties": {
      +    "country": {
      +      "description": "ISO 3166-1 alpha-2 country of this carrier.",
      +      "type": "string"
      +    },
      +    "name": {
      +      "description": "Carrier name as TVmaze records it.",
      +      "type": "string"
      +    },
      +    "timezone": {
      +      "description": "IANA timezone recorded for this carrier.",
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "name"
      +  ],
      +  "type": "object"
      +}
  2. Changed1 schema field changed
    • changedOutput schema / properties / external_id / description
      Previous value: -"Id that was looked up, as submitted."New value: +"Id looked up; IMDb ids use the canonical lowercase tt prefix and original digits."
  3. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent and openWorld, so the safety profile is covered. The description adds a behavior the annotations cannot express: a show missing from TVmaze comes back as a reported miss with guidance rather than an error, which directly changes how an agent should handle a negative result. Rate limits or lookup latency are not mentioned.

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?

Three short sentences: what it does, when to use it, and how misses behave. The main action is front-loaded and nothing is restated from the schema or annotations.

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?

With an output schema present, return values need no explanation, and the oneOf parameter structure is fully specified in the schema. The description covers the one thing structured fields can't — miss handling — leaving only minor items like the shape of that guidance implicit.

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?

Schema description coverage is 100%: each oneOf branch documents its source constant, the id pattern and a worked example. The description's enumeration of IMDb/TheTVDB/TVRage matches that, adding no format or edge-case detail beyond the schema, so the baseline 3 applies.

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 gives a specific verb and resource ("Resolve a television show from its id in another catalog") and names the three supported catalogs. That scope — an external id rather than a TVmaze id or a title — distinguishes it from tvmaze_get_show and tvmaze_search_shows without those siblings being named.

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?

"Use this to cross a show id from another source into TVmaze" states the triggering situation clearly. It stops short of naming the alternative (e.g., use tvmaze_search_shows when you only have a title) or any exclusions, so it is clear context rather than a full routing rule.

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.