TMDB MCP Server

TV Airing Today

tv_airing_today

Retrieve a list of television programs scheduled to broadcast on the current date. This tool queries The Movie Database (TMDB) to provide users with daily TV schedules.

Instructions

Get TV shows airing today

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "tv_airing_today"
  }
}

Input Schema

Name	Required	Description	Default
`page`	No	Page number (1-1000)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.1Apr 21, 2026

TDQS

C2.9/5.0

Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states what the tool does ('Get TV shows airing today') but doesn't describe how it behaves: no information about pagination (implied by the 'page' parameter but not explained), rate limits, authentication needs, data freshness, or what 'airing today' means temporally (timezone, broadcast vs. streaming). This leaves significant gaps for an agent.

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 extremely concise at four words, front-loaded with the core action and resource. Every word earns its place with no wasted text, making it easy to parse quickly.

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

Completeness2/5

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

Given the tool's moderate complexity (fetching dynamic TV data) with no annotations, no output schema, and a simple but incomplete description, this is inadequate. The description doesn't explain what 'airing today' entails, the response format, pagination behavior, or how it differs from siblings, leaving the agent with insufficient context to use it effectively.

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 has 100% description coverage for its single parameter ('page'), so the schema already documents it fully. The description adds no additional parameter semantics beyond implying pagination through the verb 'Get', which doesn't compensate or clarify beyond the schema. This meets the baseline for high schema coverage.

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?

The description 'Get TV shows airing today' clearly states the verb ('Get') and resource ('TV shows airing today'), making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'tv_on_the_air' or 'trending_tv_day' that might have overlapping functionality, preventing a perfect score.

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 provides no guidance on when to use this tool versus alternatives like 'tv_on_the_air' or 'trending_tv_day' from the sibling list. It lacks context about whether this shows currently airing episodes, upcoming premieres, or daily schedules, leaving the agent to guess based on tool names alone.

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