Skip to main content
Glama
dmang-dev

mcp-retroarch

retroarch_pause_toggle

Toggles pause state in RetroArch. Check current state with retroarch_get_status to know whether it will pause or unpause.

Instructions

Toggle the pause state. There's no separate pause/unpause command in the NCI — this single command flips the current state. Check retroarch_get_status first to know the current state.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function (switch case) that executes the retroarch_pause_toggle tool by calling ra.pauseToggle() and returning success.
    case "retroarch_pause_toggle":  await ra.pauseToggle();   return ok("Pause toggled");
  • The tool schema definition for retroarch_pause_toggle, including its name, description, and empty inputSchema.
    {
      name: "retroarch_pause_toggle",
      description: "Toggle the pause state. There's no separate pause/unpause command in the NCI — this single command flips the current state. Check `retroarch_get_status` first to know the current state.",
      inputSchema: { type: "object", properties: {} },
    },
  • src/tools.ts:176-177 (registration)
    The registerTools function registers all tools (including retroarch_pause_toggle) via ListToolsRequestSchema and handles calls via CallToolRequestSchema.
    export function registerTools(server: Server, ra: RetroArchClient): void {
      server.setRequestHandler(ListToolsRequestSchema, async () => ({ tools: TOOLS }));
  • The pauseToggle() method in RetroArchClient that sends the 'PAUSE_TOGGLE' command via fire-and-forget UDP.
    async pauseToggle():    Promise<void> { await this.send("PAUSE_TOGGLE"); }
Behavior4/5

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

Discloses that the command flips the current state (not a setter), which is the key behavioral trait. No annotations exist, so the description covers this adequately. Could be slightly more detailed about no side effects, but sufficient.

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, no fluff. Front-loaded with the action, then provides essential context. Every sentence earns its place.

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 of the tool (no params, no output schema), the description covers the toggle behavior and suggests checking status. It is complete enough for an agent to use correctly.

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?

Input schema has zero parameters; schema description coverage is 100%. With no params, baseline is 4. Description adds no parameter info, which is appropriate.

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 verb 'Toggle' and the resource 'pause state'. It differentiates from siblings by specifying that it flips state, unlike other tools like reset or frame advance.

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 advises to check retroarch_get_status first to know current state, and notes there is no separate pause/unpause command. This provides clear when-to-use guidance and context for alternatives.

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