Skip to main content
Glama

rotv-mcp

by eu.madeinro

Compare TV options side-by-side

tv_compare_options
Read-onlyIdempotent

Compares 2-5 program titles by scoring each against the chosen mood, finding the next TV airing (next 48h by default) and looking each up in the streaming catalog. Returns side-by-side breakdown and a winner with reasoning.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
moodNo
preferNo
optionsYesArray of 2-5 titles (string) or { title, channel? } objects to compare
upcoming_window_hoursNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
moodYes
winnerYes
optionsYes
freshnessYes
asked_at_utcYes
mood_label_roYes

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description adds behavioral context: scoring against mood, default 48h window, streaming lookup, and output format (side-by-side, winner). No contradiction with 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?

Two sentences, front-loaded with purpose. Every word is necessary; no redundancy.

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?

Covers most aspects: inputs (2-5 titles, mood, window), process (scoring, airing, streaming), output (breakdown, winner). Missing explanation of 'prefer' parameter. Output schema exists, so return values are handled separately.

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 description coverage is low (25%). The description explains the role of mood and upcoming_window_hours, and clarifies options. However, the 'prefer' parameter is not mentioned. Overall adds significant meaning beyond the schema.

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 verb (compares), resource (program titles), and specific actions (scoring, finding airing, looking up streaming). It distinguishes from sibling tools like tv_recommend_by_mood and tv_get_title_details.

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

Usage Guidelines3/5

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

The description implies usage when comparing options but does not explicitly state when to use vs alternatives, nor does it mention when not to use. With 13 sibling tools, more guidance is needed.

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

All rotv-mcp 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

A4.2/5.0
Disambiguation4/5

Tools are largely distinct with clear use cases, though tv_recommend_by_mood and tv_recommend_today overlap somewhat in providing ranked lists. The descriptions include guidance to prefer tv_concierge for single decisions, which helps reduce confusion.

Naming Consistency5/5

All tool names follow a consistent 'tv_' prefix with a verb_noun pattern (e.g., tv_check_freshness, tv_search_program). Minor exceptions like tv_important_today and tv_now_on_tv still adhere to the same structure, maintaining high consistency.

Tool Count5/5

With 14 tools, the set is well-scoped for a comprehensive TV and streaming recommendation service. Each tool addresses a specific user need without being excessive, making the set appropriate for the domain.

Completeness4/5

The tool set covers key operations: search, recommendations (single, list, for couples), planning, prime-time/now, important events, and details. Minor gaps like user preference storage are absent, but the coverage is sufficient for most user queries.

Resources