Skip to main content
Glama
0xpolarzero

luda

by 0xpolarzero
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

desktop_invoke

Invoke desktop element actions (e.g., buttons) without activating windows. Handles single-action elements automatically and lets you specify exact action for multiple.

Instructions

Invoke the sole action returned by inspect, or supply its exact action name. Native actions address the control without activating its window; application callbacks may bring windows forward. Multiple actions require an explicit choice; no click/press naming guess is needed for a single-action button. Completion means dispatch, not verified application outcome.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actionNo
element_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv0.3.4
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / action / anyOf
      Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
    • addedInput schema / properties / action / default
      Added value: +null
    • removedInput schema / properties / action / type
      Removed value: -"string"
    • changedInput schema / required
      Previous value: -[
-  "element_id",
-  "action"
-]New value: +[
+  "element_id"
+]
  2. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations provided, the description carries the behavioral burden and does a good job: it discloses that native actions do not activate the window, application callbacks may bring windows forward, and completion means dispatch rather than verified outcome. This is valuable behavioral context beyond the schema.

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?

The description is reasonably concise and front-loaded with the primary purpose. Each sentence adds information, though the third sentence somewhat restates the first regarding action naming, so it could be slightly tighter. Overall, it avoids fluff and stays readable.

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?

Given there is no output schema and no annotations, the description covers the most important operational details: how to select the action, window-activation behavior, and the meaning of completion. It lacks an explicit note about what the function returns, but the dispatch-vs-outcome statement partially addresses that concern.

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

Parameters3/5

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

Schema coverage is 0%, so the description must compensate. It clearly explains the 'action' parameter semantics: it can be the sole action from inspect, an exact action name, or omitted when there is a single action. However, the required 'element_id' parameter is not addressed at all, leaving one of two parameters underspecified.

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 states a clear verb and resource: 'Invoke the sole action returned by inspect, or supply its exact action name.' It also distinguishes the tool from click/press-based siblings by noting that no naming guess is needed for a single-action button, making the tool's unique role explicit.

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 gives concrete guidance on when to use this tool: after inspect returns an action, or when you know the exact action name. It also notes that multiple actions require an explicit choice, which helps the agent decide when additional information is needed. It does not explicitly name alternative tools, but the click/press contrast implies the boundary.

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