rotv-mcp

Search Romanian TV programs

tv_search_program

Read-onlyIdempotent

Search programs across all Romanian TV channels in the guide by free-text title, channel, category, and time window. Use for queries like "documentaries on Discovery tomorrow", "football on Saturday", "what is on Antena 1 right now". Time references accepted: now, tonight, tomorrow, weekend, primetime, today, YYYY-MM-DD, ISO instant, or ISO range "A/B".

Input Schema

Name	Required	Description	Default
`limit`	No
`query`	No	Free text to match against program title (case/diacritic-insensitive)
`channel`	No	Channel id, display name, or alias (e.g. "PRO TV", "tv-pro-tv", "HBO")
`category`	No	Channel category: Generaliste \| Știri \| Sport \| Filme & Seriale \| Documentare \| Copii \| Muzică \| Altele
`timeframe`	No	Natural time reference: now \| tonight \| tomorrow \| weekend \| primetime \| today \| YYYY-MM-DD \| ISO instant \| ISO range "A/B"	now
`exclude_news`	No

Output Schema

Name	Required	Description	Default
`count`	Yes
`items`	Yes
`window`	Yes
`asked_at_utc`	Yes
`generated_at`	No
`channel_match`	No
`timeframe_label`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 31, 2026

addedOutput schema / properties / channel_match

Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "channel_ids": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "channels": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "match": {
+      "enum": [
+        "exact",
+        "approximate",
+        "none"
+      ],
+      "type": "string"
+    },
+    "matched_by": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "query": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "query",
+    "match",
+    "matched_by",
+    "channel_ids",
+    "channels"
+  ],
+  "type": "object"
+}

First observedJul 8, 2026

TDQS

B3.2/5.0

Behavior3/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive). The description adds the detail that the search is 'in the guide,' implying data source and freshness context, but does not disclose other behavioral traits like rate limits, result pagination, or how no-results are handled.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded with purpose and examples, and is appropriately concise. The time references sentence is slightly redundant with the schema but does not bloat the description significantly.

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

Completeness3/5

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

An output schema exists, so return values need not be described. However, the description is incomplete regarding the limit and exclude_news parameters, and does not clarify search behavior or edge cases for a tool with six optional parameters.

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

Parameters2/5

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

Schema description coverage is 67%, and the description repeats the exact time reference list already present in the schema, adding no new meaning for any parameter. It also fails to document the two undocumented parameters (limit and exclude_news).

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?

States a specific verb (Search) and resource (programs across all Romanian TV channels) with multiple searchable fields. It clearly conveys the tool's scope, but does not explicitly differentiate itself from sibling tools like tv_now_on_tv or tv_get_prime_time.

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?

Provides example queries that imply typical usage, but gives no explicit guidance on when to use this tool versus alternatives. The example 'what is on Antena 1 right now' overlaps with sibling tools, and the description does not clarify the distinction.

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

All rotv-mcp tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.