Skip to main content
Glama
dmang-dev

mcp-retroarch

retroarch_frame_advance

Advance one frame at a time in retro gaming emulation. Use with pause toggle for frame-by-frame analysis.

Instructions

Step exactly one frame forward. Only effective while paused; pause first with retroarch_pause_toggle.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • src/tools.ts:107-111 (registration)
    Tool definition/registration for retroarch_frame_advance in the TOOLS array with name, description, and empty inputSchema.
    {
      name: "retroarch_frame_advance",
      description: "Step exactly one frame forward. Only effective while paused; pause first with `retroarch_pause_toggle`.",
      inputSchema: { type: "object", properties: {} },
    },
  • The switch-case handler that executes retroarch_frame_advance by calling ra.frameAdvance() and returning a success message.
    case "retroarch_frame_advance": await ra.frameAdvance();  return ok("Advanced one frame");
  • The RetroArchClient.frameAdvance() method that sends the UDP command 'FRAMEADVANCE' via the fire-and-forget send() helper.
    async frameAdvance():   Promise<void> { await this.send("FRAMEADVANCE"); }
Behavior4/5

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

No annotations provided, but description covers key behavior: stepping one frame forward, only effective when paused. It doesn't detail what happens if called while not paused (likely no-op), but overall adequate.

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, front-loaded with action and condition. Every sentence is necessary; no fluff.

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?

For a zero-parameter tool with no output schema, the description completely captures usage context: when to use (after pause), what it does (step one frame), and prerequisite. No missing information.

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?

No parameters exist, so schema coverage is 100%. Baseline score of 4 is appropriate; description adds no param info because none needed.

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?

Description clearly states 'Step exactly one frame forward', specifying the action and resource. It distinguishes from siblings by noting it requires paused state, referencing the pause toggle tool.

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 says 'Only effective while paused; pause first with retroarch_pause_toggle', providing direct when-to-use guidance and referencing an alternative prerequisite tool.

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