Skip to main content
Glama

cast

Send local media to a TV on your network over DLNA: list renderers, start or stop casting, then pause, resume, seek, and check status of playback.

Instructions

Send what is playing to a television on the network over DLNA. "list" finds renderers; "to" starts a cast (naming a renderer, or omitting it when there is only one) and pauses playback here so it is not heard twice; "stop", "pause", "resume", "seek" and "status" drive it once it is running. Only local files can be cast — the television fetches them from this machine.

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

Input Schema

NameRequiredDescriptionDefault
fileNoA file to cast instead of what is playing.
actionNoDefaults to status.
secondsNoFor seek, where to go. For list and to, how long to wait for renderers to answer (default 3).
rendererNoWhich renderer, by name or part of it. Omit when there is only one.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and discloses two genuinely non-obvious behaviors: "to" pauses local playback so audio is not heard twice, and only local files can be cast because the television fetches them from this machine. It omits failure handling and whether local playback resumes after "stop"/"pause", which keeps it below a 5.

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?

Three compact sentences, front-loaded with the purpose and followed by an action map and the key constraint. Quoted action names make it scannable, though the density of semicolon-separated clauses is near the limit before it becomes a spec dump.

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?

For a 4-parameter, annotation-free, no-output-schema tool, this covers purpose, action modes, renderer selection, and the local-file constraint. The remaining gap is return behavior for "list" and "status" and what happens when a renderer is unreachable.

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%, so the schema already documents file, action, seconds, and renderer, including the renderer-omission rule repeated in the description. The description adds little parameter meaning beyond restating the modes, so the baseline 3 applies.

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?

Opens with a specific verb+resource ("Send what is playing to a television on the network over DLNA") and then enumerates the action modes, so the agent knows exactly what the tool spans. It stops short of distinguishing its pause/stop/seek actions from the sibling tools of the same names, which is the one ambiguity an agent could trip on.

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?

Gives concrete routing guidance: use "list" to find renderers, "to" to start a cast, name a renderer or omit it when there is only one. It does not state when to prefer the sibling pause/stop/seek tools over the cast actions, or what to do when no renderer responds, but the in-tool usage is clear.

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

Deploy Server

Other Tools