Skip to main content
Glama
bdstark

gma3-mcp

by bdstark
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Press a PC key with explicit modifiers

gma3_keyboard

Simulate raw PC key taps, presses, and releases in grandMA3 onPC with explicit Shift, Ctrl, Alt, and Num Lock modifiers via its Keyboard emulation.

Instructions

Press, release or tap a raw PC key (case-sensitive Enums.KeyboardCodes name: Enter, Escape, F1, 5, A, LeftShift ...) with shift/ctrl/alt/numlock passed explicitly on the press AND the release, through the console's Keyboard() emulation. What the key does depends on the operator's user profile, keyboard shortcut enablement and the focused UI element (a mapped key may edit a focused field instead of acting as a hardkey); nothing is substituted or resolved for you, prefer gma3_hardkey for MA keys. tap returns after the release was attempted; press REQUIRES an interaction id; release uses the stored press tuple. Same gate, ownership, busy and verification rules as gma3_hardkey: real keys, input OFF until the operator runs Plugin "gma3_mcp_bridge" "input=keyboard", not display-scoped, commands from every client are [busy] while a key is held, UI effect unverified, nothing retried or replayed.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
altNoPC modifier passed explicitly on the press and the release (one event with the flag; no modifier key is pressed separately). Only with pc_key.
ctrlNoPC modifier passed explicitly on the press and the release (one event with the flag; no modifier key is pressed separately). Only with pc_key.
shiftNoPC modifier passed explicitly on the press and the release (one event with the flag; no modifier key is pressed separately). Only with pc_key.
actionYes
pc_keyYesCase-sensitive Enums.KeyboardCodes name as the console spells it (Enter, Escape, LeftShift, F1, 5, A). Validated on the console before dispatch.
displayNoDisplay index passed to the console as API context only. It must exist; input is NOT display-scoped on onPC 2.5.1 (no routing, focus or pop-up placement is promised).
hold_msNotap only (default 50).
numlockNoNumlock flag passed explicitly on both events. Only with pc_key.
exclusiveNoThe intended long-press (see gma3_hardkey).
interactionNoId from gma3_input_interaction acquire. Required for a standalone hold (press). A bounded tap, chord tap, text or sequence may run without one (it owns an interaction for its duration) but must pass the id while this server has one open.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.8/5.0
Behavior5/5

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

With no annotations, the description carries the full burden and succeeds: it discloses that keys are real, input is OFF until the operator loads the plugin, commands are [busy] while a key is held, the UI effect is unverified, and nothing is retried or replayed. It also specifies lifecycle semantics (tap returns after release attempted, press requires an interaction id, release uses the stored press tuple).

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the verb+resource, and nearly every sentence conveys operationally useful constraints rather than filler. It is a dense run-on paragraph with a few formatting artifacts (double spaces inside the quoted plugin invocation), which costs a point but not the underlying value.

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 10-parameter, non-idempotent input tool with no output schema and no annotations, the description covers gating, ownership, busy state, verification expectations and action semantics. Nothing an agent needs to invoke it correctly is missing.

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 already 90%, so the baseline is 3, but the description adds real procedural meaning the schema does not: the action-dependent requirements (press needs an interaction id; release reuses the stored press tuple), and that modifiers are passed on both the press and the release rather than as separate key presses. Only the hold_ms/display/exclusive details remain schema-only.

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?

States specific verbs (press, release, tap) on a specific resource (raw PC key via Enums.KeyboardCodes) and explains the mechanism (console Keyboard() emulation). It explicitly distinguishes itself from gma3_hardkey, so an agent can route between them without opening a schema.

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 to prefer gma3_hardkey for MA keys, warns that behavior depends on user profile, shortcut enablement and focused UI element, and enumerates prerequisites (input OFF until the operator runs the plugin, ownership/busy rules). When-to-use and when-to-use-something-else are both given.

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

Deploy Server

Other Tools