Skip to main content
Glama

mister_launch

Launch a MiSTer game by title or start a system core directly, displaying it on an already-on TV when input switching is available.

Instructions

Start a game or a core. Game: words of its title. System: its name, alone to start its core with no game. Then the TV it is plugged into shows it, only if that TV is already on.

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

Input Schema

NameRequiredDescriptionDefault
gameNo
systemNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations only declare readOnlyHint=false, so the description must add the behavioral detail, and it does contribute one real trait: the result is displayed on the TV the device is plugged into, and only if that TV is already powered on. It omits other useful context for a mutating launch, such as whether the current game is terminated, whether confirmation is required, or latency.

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 purpose is front-loaded in the first clause, followed by per-parameter guidance and the side-effect note; there is little filler. The phrasing is clipped and slightly awkward ('System: its name, alone to start its core with no game'), which costs a point.

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?

With an output schema present, return values need not be explained, but the description still leaves gaps for a mutation tool: no statement about what happens when both arguments are null, what occurs to a running game, or whether a follow-up confirm step exists in this tool family. It is minimally adequate rather than complete.

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 0%, so the description must carry the burden; it does explain the expected value shape for each parameter (title words vs. bare system name). However, with two optional, nullable parameters it never states precedence when both are given, whether either is required, or whether matching is case-sensitive.

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 opens with a specific verb+resource ('Start a game or a core') and then distinguishes the two modes it can start. It is identifiable against siblings like mister_status or mister_search, though the launch/launch_confirm split is never named.

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?

It gives implied usage guidance by explaining how to invoke each mode ('words of its title' for game, 'its name, alone to start its core with no game'). It says nothing about when this tool should be used instead of mister_launch_confirm, nor what happens if both or neither argument is supplied.

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