Skip to main content
Glama

desktop_cursor_overlay_disable

Disables the cursor overlay for a selected desktop session, removing the visual pointer marker when it is not needed.

Instructions

agent-desktop cursor-overlay disable: Disable the cursor overlay for the selected session

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "desktop_cursor_overlay_disable"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full disclosure burden. It reveals only that this toggles a visual overlay off for a session and says nothing about whether the change is reversible, whether it persists, permissions required, or error behavior when no session is selected.

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?

One short, front-loaded sentence with no filler. The only waste is the redundant "agent-desktop cursor-overlay disable:" prefix, which repeats the tool name rather than adding information.

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-parameter toggle with no output schema, the definition is nearly sufficient: purpose and target scope are stated. Only the side effects on session/overlay state and the implicit precondition of a selected session are left implicit.

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?

The tool takes zero parameters, which sets the baseline at 4. The phrase "the selected session" usefully flags that session state is external context even though no parameter is involved.

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 and resource: "Disable the cursor overlay for the selected session." It is unmistakable what the tool does, though it does not name the obvious counterpart (desktop_cursor_overlay_enable) to sharpen the distinction, and the "agent-desktop cursor-overlay disable:" prefix merely restates the tool name.

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 only implied by "for the selected session," which hints that a session must already be selected, but the description never says when to disable versus enable, nor what happens if no session exists. No explicit exclusions or alternatives are given.

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