Skip to main content
Glama
dmang-dev

mcp-retroarch

retroarch_reset

Perform a hard reset on the currently running game, equivalent to pressing the console's reset button.

Instructions

Hard-reset the running game (equivalent to pressing the console's reset button).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • src/tools.ts:112-115 (registration)
    Tool definition (name, description, schema) registered in the TOOLS array for retroarch_reset
    {
      name: "retroarch_reset",
      description: "Hard-reset the running game (equivalent to pressing the console's reset button).",
      inputSchema: { type: "object", properties: {} },
  • Handler case in CallToolRequestSchema switch — calls ra.reset() and returns 'Game reset'
    case "retroarch_reset":         await ra.reset();         return ok("Game reset");
  • RetroArchClient.reset() method — sends 'RESET' UDP command (fire-and-forget)
    async reset():          Promise<void> { await this.send("RESET"); }
Behavior3/5

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

The description conveys core behavior (hard reset) but does not disclose side effects like loss of unsaved progress, prerequisites (game running), or behavior if no game is loaded. With no annotations, more detail would help.

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?

The description is a single, efficient sentence that is front-loaded with the action. Every word is necessary and earns its place.

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?

Given the tool has no parameters, no output schema, and a simple behavior, the description is complete enough. It tells what the tool does and how, requiring no further elaboration.

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?

There are no parameters, so schema coverage is 100%. The description adds meaning beyond the schema by explaining the tool's action. Baseline for 0 parameters is 4, and the description meets that.

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 performs a hard-reset of the running game, using a known analogy (pressing reset button). It distinguishes from siblings like load_state or pause_toggle.

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?

The description implies usage when a game reset is needed but lacks explicit guidance on when not to use (e.g., losing unsaved progress) or alternatives. It is clear but has no exclusions.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/dmang-dev/mcp-retroarch'

If you have feedback or need assistance with the MCP directory API, please join our Discord server