Skip to main content
Glama

press

Simulate a DualSense button press for AI-driven game and app control, with a configurable hold duration that keeps the button down as long as needed.

Instructions

Press a DualSense button: cross, circle, square, triangle, dpad_up/down/left/right, l1, r1, l2, r2, l3, r3, options, share, touchpad, ps. hold_ms is how long the button stays down.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "button": "<button>"
    },
    "name": "press"
  }
}

Input Schema

NameRequiredDescriptionDefault
buttonYes
hold_msNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

A3.5/5.0
Behavior2/5

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

No annotations are supplied, so the description bears the full burden. It discloses one key behavior — hold_ms controls how long the button stays down — but never says whether the button is automatically released afterward, whether the call blocks, or what happens with an invalid button name.

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 with the resource and valid values front-loaded and the one behavioral parameter explained last. The long button list is necessary given the missing enum and nothing is wasted.

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?

For a two-parameter, annotation-free tool with no output schema, this covers the essentials: what to press, allowed values, and hold duration. The remaining gap is the press/release lifecycle and error handling, which an agent could plausibly need.

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?

Schema coverage is 0% and the button parameter has no enum, so the enumeration of accepted values in the description is essential and well done. hold_ms is also given meaning ('how long the button stays down') beyond its title. It stops short of case-sensitivity or error behavior for unknown values.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb (press) and resource (a DualSense button) and enumerates the valid button identifiers, making the tool's domain clear. It implicitly distinguishes itself from keyboard/mouse siblings by naming the DualSense controller, but never names a sibling directly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied by the verb — press one button — but there is no explicit guidance on when to prefer this over combo (multi-button), hold_stick, or release_all, nor any stated prerequisite such as an active device connection.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.