Skip to main content
Glama
dmang-dev

mcp-retroarch

retroarch_show_message

Show an on-screen notification in RetroArch to provide user feedback or debug information during script execution.

Instructions

Display a notification message overlaid on the RetroArch window. Useful for debugging or telling the user something during a long-running script.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
messageYesMessage text. Spaces are kept; line breaks are not.

Implementation Reference

  • Tool schema definition for retroarch_show_message, defining the 'message' string input parameter.
    {
      name: "retroarch_show_message",
      description: "Display a notification message overlaid on the RetroArch window. Useful for debugging or telling the user something during a long-running script.",
      inputSchema: {
        type: "object",
        required: ["message"],
        properties: {
          message: { type: "string", description: "Message text. Spaces are kept; line breaks are not." },
        },
      },
    },
  • Handler that calls ra.showMessage() with the message argument and returns a confirmation string.
    case "retroarch_show_message": {
      await ra.showMessage(p.message as string);
      return ok(`Showed: ${p.message}`);
    }
  • Helper method in RetroArchClient that sends the SHOW_MSG command with the message text via UDP to RetroArch's Network Control Interface.
    async showMessage(msg: string): Promise<void> { await this.send(`SHOW_MSG ${msg}`); }
Behavior4/5

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

With no annotations, the description carries the full burden. It accurately describes the tool's behavior as displaying a notification message. While it does not mention non-blocking behavior or side effects, for a simple display tool this is 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?

The description is two sentences totaling ~20 words, with the main action in the first sentence. No unnecessary information is included.

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?

The tool is simple with a single parameter and no output schema. The description fully explains its purpose and typical use, making it contextually complete for an agent.

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 100% (single parameter 'message' with description). The tool description does not add any information beyond what is in the schema, so baseline 3 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 tool displays a notification message overlaid on the RetroArch window. It distinguishes itself from siblings like retroarch_ping and retroarch_screenshot by specifying the overlay notification functionality.

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 description provides a clear usage context ('useful for debugging or telling the user something during a long-running script') but does not explicitly mention when not to use it or suggest 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