Skip to main content
Glama

ppsspp_get_info

Retrieve the currently loaded game's title, disc ID, and version, along with PPSSPP's emulation state (running, paused, or stepping). Returns 'no game loaded' fields if at home menu.

Instructions

PURPOSE: Get the loaded game's title, disc ID, and version, plus PPSSPP's run state. USAGE: Call after ppsspp_ping to learn what game is loaded and whether emulation is currently running or stepping. BEHAVIOR: No side effects — pure read. Returns 'no game loaded' fields if PPSSPP is at the home menu / not currently emulating. RETURNS: Multi-line text with Title, Disc ID, Version, and run state (running / paused / stepping).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Schema/definition of the ppsspp_get_info tool in the TOOLS array: name, description, and empty input schema (no parameters).
    {
      name: "ppsspp_get_info",
      description:
        "PURPOSE: Get the loaded game's title, disc ID, and version, plus PPSSPP's run state. " +
        "USAGE: Call after ppsspp_ping to learn what game is loaded and whether emulation is currently running or stepping. " +
        "BEHAVIOR: No side effects — pure read. Returns 'no game loaded' fields if PPSSPP is at the home menu / not currently emulating. " +
        "RETURNS: Multi-line text with Title, Disc ID, Version, and run state (running / paused / stepping).",
      inputSchema: { type: "object", properties: {} },
  • Handler execution logic for ppsspp_get_info: calls PPSSPP's 'game.status' event via WebSocket, extracts game title/disc ID/version and emulator state (running/paused/stepping), returns formatted multi-line text.
    case "ppsspp_get_info": {
      const status = await pp.call<{ game?: { id?: string; title?: string; version?: string } | null; paused?: boolean; stepping?: boolean }>("game.status");
      const lines: string[] = [];
      if (status.game) {
        lines.push(`Title:   ${status.game.title ?? "(unavailable)"}`);
        lines.push(`Disc ID: ${status.game.id ?? "(unavailable)"}`);
        lines.push(`Version: ${status.game.version ?? "(unavailable)"}`);
      } else {
        lines.push("No game loaded.");
      }
      const state = status.stepping ? "stepping (paused)" : status.paused ? "paused" : "running";
      lines.push(`State:   ${state}`);
      return ok(lines.join("\n"));
    }
  • src/tools.ts:405-406 (registration)
    Registration of all tools (including ppsspp_get_info) via server.setRequestHandler with ListToolsRequestSchema, exposing the TOOLS array.
    export function registerTools(server: Server, pp: PpssppClient): void {
      server.setRequestHandler(ListToolsRequestSchema, async () => ({ tools: TOOLS }));
Behavior5/5

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

Clearly states no side effects (pure read) and describes the 'no game loaded' edge case. With no annotations provided, the description fully informs the agent of behavioral traits.

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?

Very concise, structured with labeled sections (PURPOSE, USAGE, BEHAVIOR, RETURNS). Every sentence adds value. Front-loaded with key information.

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?

Completes the picture for a read-only tool with no output schema: explains return format (multi-line text) and edge case. No gaps for the intended use.

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 no additional meaning needed. Baseline for 0 params is 4. Description does not need to cover parameter details.

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?

Explicitly states it gets the game's title, disc ID, version, and PPSSPP's run state. Clearly distinguishes from siblings like ppsspp_ping and ppsspp_get_registers by focusing on game metadata and emulation state.

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?

Advises calling after ppsspp_ping to learn the loaded game and run state. Provides context on when to use but does not explicitly list alternatives or when not to use.

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-ppsspp'

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