Skip to main content
Glama

ppsspp_send_analog

Send analog stick input to the PSP emulator for controlling character movement or camera angles. Accepts x and y values from -1 to 1 for precision.

Instructions

PURPOSE: Set the PSP analog stick state (one of left/right; the PSP only has one stick natively but PPSSPP exposes both for forward-compat). USAGE: Drive games that need analog input — character movement, camera control. X and Y are signed in [-1.0, 1.0]; (0, 0) = neutral, (1, 0) = full right, (0, -1) = full up. BEHAVIOR: Modifies emulator analog input. State persists until updated. RETURNS: Single line 'Set analog stick STICK to (X, Y)'.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
stickYesWhich analog stick to update. PSP only has 'left' natively; 'right' is reserved.
xYesHorizontal axis. -1 = full left, 0 = center, 1 = full right.
yYesVertical axis. -1 = full down, 0 = center, 1 = full up.

Implementation Reference

  • Tool schema definition for 'ppsspp_send_analog' — declares name, description, inputSchema with required stick/x/y parameters (stick enum left/right, x and y in [-1,1]).
    {
      name: "ppsspp_send_analog",
      description:
        "PURPOSE: Set the PSP analog stick state (one of left/right; the PSP only has one stick natively but PPSSPP exposes both for forward-compat). " +
        "USAGE: Drive games that need analog input — character movement, camera control. X and Y are signed in [-1.0, 1.0]; (0, 0) = neutral, (1, 0) = full right, (0, -1) = full up. " +
        "BEHAVIOR: Modifies emulator analog input. State persists until updated. " +
        "RETURNS: Single line 'Set analog stick STICK to (X, Y)'.",
      inputSchema: {
        type: "object",
        required: ["stick", "x", "y"],
        properties: {
          stick: { type: "string", enum: ["left", "right"], description: "Which analog stick to update. PSP only has 'left' natively; 'right' is reserved." },
          x: { type: "number", minimum: -1, maximum: 1, description: "Horizontal axis. -1 = full left, 0 = center, 1 = full right." },
          y: { type: "number", minimum: -1, maximum: 1, description: "Vertical axis. -1 = full down, 0 = center, 1 = full up." },
        },
        additionalProperties: false,
      },
    },
  • Handler for 'ppsspp_send_analog' — calls PPSSPP's 'input.analog.send' RPC with the stick/x/y parameters and returns confirmation.
    case "ppsspp_send_analog": {
      await pp.call("input.analog.send", { stick: p.stick, x: p.x, y: p.y });
      return ok(`Set analog stick ${p.stick} to (${p.x}, ${p.y})`);
    }
  • src/tools.ts:405-412 (registration)
    Registration of all tools — the TOOLS array (including ppsspp_send_analog) is registered via ListToolsRequestSchema handler, and CallToolRequestSchema routes to the switch-case handler.
    export function registerTools(server: Server, pp: PpssppClient): void {
      server.setRequestHandler(ListToolsRequestSchema, async () => ({ tools: TOOLS }));
    
      server.setRequestHandler(CallToolRequestSchema, async (req) => {
        const { name, arguments: args = {} } = req.params;
        const p = args as Record<string, unknown>;
        const a = () => p.address as number;
Behavior4/5

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

Without annotations, the description discloses that state persists until updated and returns a confirmation line. However, it does not mention side effects or restrictions like need for a running game, which would provide fuller transparency.

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 well-structured with labeled sections (PURPOSE, USAGE, BEHAVIOR, RETURNS) and no unnecessary words, making it highly concise and readable.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple analog stick tool, the description covers purpose, usage, and return value. However, the contradiction between schema and description on the y-axis and lack of mention of the 'right' stick's reserved status leaves a notable gap.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The description adds meaning with coordinate examples, but it contradicts the schema on the y-axis sign: description says (0,-1)=full up while schema says -1=full down. This inconsistency undermines clarity for a critical axis.

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 sets the PSP analog stick state, specifies it's for one of left/right, and notes the PSP only has one stick natively but PPSSPP exposes both, which distinguishes it from sibling tools like ppsspp_press_button.

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 usage context (drive games needing analog input) and implicit differentiation from digital button tools, but does not explicitly state when not to use it or recommend 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-ppsspp'

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