Skip to main content
Glama
Sign In
wasabi

wasabi

by creep-ltx
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Remote

Use the mouse

amiga_mouse

Move the pointer to x,y and click, double-click, press, or release a mouse button on the Amiga front screen; omit coordinates to act at the current pointer. Use it for icons and custom-drawn areas.

Instructions

Move the pointer to x,y and/or click there with the real mouse: move, click, doubleclick, or press (down) and release (up) a button. Without x,y it acts where the pointer is. Coordinates as in amiga_screenshot. Prefer amiga_ui_click when the target is a named gadget; use this for icons and custom-drawn areas. For a whole drag use amiga_drag.

Input Schema

NameRequiredDescriptionDefault
xNox on the front screen
yNoy on the front screen
actionNomove, click (default), doubleclick, down or up
buttonNoleft (default), right or middle

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv0.1.1
    • changedInput schema / properties / action / description
      Previous value: -"move, click, doubleclick, down or up"New value: +"move, click (default), doubleclick, down or up"
    • addedInput schema / properties / action / enum
      Added value: +[
+  "move",
+  "click",
+  "doubleclick",
+  "down",
+  "up"
+]
    • addedInput schema / properties / button / enum
      Added value: +[
+  "left",
+  "right",
+  "middle"
+]
    • changedInput schema / properties / x / description
      Previous value: -"x"New value: +"x on the front screen"
    • changedInput schema / properties / y / description
      Previous value: -"y"New value: +"y on the front screen"
  2. First observedv0.1.0

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare the mutating, non-idempotent, non-destructive profile, so the bar is lower. The description adds real context beyond them: it drives the actual system pointer, coordinates follow the amiga_screenshot frame, and omitting x/y acts at the current pointer location. It does not describe the response or any side effects of the click itself (e.g. focus changes), which keeps it below a 5.

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?

Three compact sentences: capability first, coordinate frame second, sibling routing last. Every clause carries information (modes, defaults, coordinate reference, alternatives) with no filler.

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 zero-required-parameter pointer tool with no output schema and full schema coverage, the description covers modes, defaults, coordinate frame, and alternatives. The only unaddressed item is what a click returns or what UI state it may change, which is a minor gap given annotations cover the mutation profile.

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 100% and enums are already documented, so the baseline is 3. The description still adds meaning the schema lacks, notably that x and y are optional together (omitting them acts at the pointer) and that the coordinate system matches amiga_screenshot, which disambiguates what 'front screen' coordinates mean.

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 pairs a specific verb set (move, click, doubleclick, down/up) with a concrete resource (the real mouse pointer on the front screen) and states the no-coordinate behavior. It actively distinguishes itself from sibling tools by naming amiga_ui_click and amiga_drag.

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?

Explicit routing is given: prefer amiga_ui_click for named gadgets, use this tool for icons and custom-drawn areas, and use amiga_drag for a whole drag. Both an inclusion rule and two exclusions are stated, so an agent can pick between the three pointer tools without opening schemas.

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