Trigger desktop keyboard shortcuts by sending 2-4 simultaneous keys, such as Ctrl+T or Alt+Tab, through Astrax.
Atajo de 2-4 teclas simultáneas, p. ej. ["ctrl","t"], ["ctrl","l"], ["alt","tab"].
| Name | Required | Description | Default |
|---|---|---|---|
| teclas | Yes |
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden. It discloses simultaneity and the 2-4 key range as behavioral traits beyond the schema, but omits prerequisites such as window focus, OS support, error behavior, and whether keys are held or released.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
A single telegraphic sentence with examples; there is no wasted text and the key constraint is front-loaded. It is slightly fragmentary but appropriately sized for the tool.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
An output schema exists, so return values need not be explained. For a one-parameter UI shortcut tool the input format is covered, but missing usage context and behavioral prerequisites leave gaps given that no annotations are present.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0% and the single parameter has no schema description. The text compensates by defining teclas as 2-4 simultaneous key names and giving examples like ["ctrl","t"] and ["alt","tab"], adding meaning beyond a raw array-of-strings schema.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific resource (keyboard shortcut) and scope (2-4 simultaneous keys) with examples. It implicitly distinguishes itself from the single-key sibling astrax_tecla by requiring simultaneous keys, but does not name the alternative explicitly.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The examples show invocation format but there is no explicit when-to-use or when-not-to-use guidance. The 2-4 simultaneous constraint implies usage for key combinations, but no alternative routing is provided.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.