Skip to main content
Glama

Return to the MiSTer menu

mister_return_to_menu
DestructiveIdempotent

Exits the active game and reloads the MiSTer main menu core. Use it to stop play immediately; unsaved progress is lost.

Instructions

<use_case> Exit the active game and reload the MiSTer main menu core. </use_case> <important_notes>

  • DESTRUCTIVE: Unsaved game progress will be lost.

  • If host is omitted, acts on whichever MiSTer is currently running a game. </important_notes>

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_return_to_menu"
  }
}

Input Schema

NameRequiredDescriptionDefault
hostNoMiSTer name from mister_get_status. Omit when the call already says which (a ref does).

Output Schema

NameRequiredDescriptionDefault
resultsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, but the description adds the concrete consequence — unsaved game progress is lost — plus what happens when host is omitted (acts on whichever MiSTer is running a game). That is real behavioral context beyond the annotations, though it doesn't cover permissions or post-exit state.

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 short structured blocks with the action first and the risk second; every sentence carries information and nothing is redundant.

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

Completeness5/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, there is a single fully documented optional parameter, and the destructive risk and default-targeting behavior are both disclosed. Nothing needed to invoke it correctly is missing.

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 coverage is 100%, so the baseline is 3; the description exceeds it by explaining the default-host behavior (targets whichever MiSTer is currently running a game), which the schema's 'default: null' does not convey.

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?

States a specific verb+resource pair: 'Exit the active game and reload the MiSTer main menu core.' An agent can distinguish this from mister_launch (which starts a game) purely from this sentence.

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?

The use_case block clearly frames when to call it, and the note about omitting host clarifies a conditional usage path. It does not explicitly name an alternative tool for the opposite action (launching), so this stops short of a 5.

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