kde-desktop-mcp

Overview Schema Source Related Servers Discussions Admin

kde_pointer_position

Read-only

Read the current mouse pointer coordinates in a chosen KDE session without moving the cursor, so you can inspect position or debug placement.

Instructions

Read the selected session's current pointer position without moving it.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "session": "<session>"
    },
    "name": "kde_pointer_position"
  }
}

Input Schema

Name	Required	Description	Default
`session`	Yes	Required target selector: a managed private session ID, or the exact value 'user-desktop' to explicitly opt into the real user desktop.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 13, 2026

TDQS

A3.5/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, and 'without moving it' reinforces a non-mutating read, so the safety profile is covered twice. The description adds nothing about the return format (coordinates, coordinate space, multi-monitor handling), which is unaddressed by annotations and there is no output schema.

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?

One front-loaded sentence with zero wasted words; the read-only constraint is stated immediately after the action.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple single-parameter read this is nearly complete, but with no output schema the description should say what comes back (screen coordinates, which coordinate space/monitor) so an agent can chain it into kde_input_click_at or kde_input_drag. That return-value gap is the main missing piece.

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 100% and the single 'session' parameter is fully documented in-schema, including the 'user-desktop' opt-in and the agent-session pattern. The description's 'selected session' wording slightly reinforces the selector semantics but adds no format or scope detail beyond the schema, so the baseline 3 applies.

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?

States a specific verb and resource ('Read ... current pointer position') scoped to 'the selected session'. The clause 'without moving it' implicitly separates it from the kde_input_* mutation tools, though no sibling is named.

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?

The phrase 'the selected session's' hints that a session must already be selected (e.g. via kde_session_use) before calling, which is useful implied context. However, there is no explicit when-to-use/when-not guidance and no named alternative for actually moving or clicking the pointer.

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