aria-mcp-tvguide-dk

tonight

Retrieve tonight's prime-time TV schedule (19:00-23:00) for Danish channels. Accepts an optional list of channels to override defaults.

Instructions

Return prime-time (19:00–23:00 Copenhagen) TV listings for today for the default channel set (DR1, DR2, TV 2, TV 2 News, TV3, TV3+, Kanal 4, Kanal 5, TV 2 Charlie, 6'eren — or as configured by DEFAULT_CHANNELS env). Accepts an optional channel list to override the default. Use this when asked 'hvad går der i fjernsynet i aften?' or 'hvad er på programmet i aften?'.

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": "tonight"
  }
}

Input Schema

Name	Required	Description	Default
`channels`	No	Optional list of channel names or ids to include. Defaults to the configured default channel set.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jun 12, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Describes key behaviors: time range, default channels, and optional override. No annotations exist, but description is adequate for a read-only operation.

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 with critical information front-loaded. No unnecessary words, and the usage guidance is efficiently appended.

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?

Given the simplicity (one optional parameter, no output schema), the description covers purpose, usage, and behavior sufficiently. Could mention that it returns data for 'today' but it's implied.

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?

The schema already describes the parameter. The description adds context that the channel list overrides defaults, which slightly enhances understanding 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 tool returns prime-time TV listings for today, specifying the time range and default channel set. It distinguishes itself from siblings like 'list_channels' and 'search_program' by focusing on prime-time tonight.

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 provides when to use the tool with specific example queries ('hvad går der i fjernsynet i aften?'), guiding the agent appropriately.

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

Deploy Server