Skip to main content
Glama
Sign In
zandronum-mcp

zandronum-mcp

by rc4l
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Scroll the mouse wheel

mouse_wheel

Simulate mouse wheel scrolling in Zandronum by sending wheel notches at the current pointer position. Use positive values to scroll up and negative values to scroll down.

Instructions

Wheel notches at the current pointer position. Positive scrolls up, negative down.

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": {
      "notches": "<notches>"
    },
    "name": "mouse_wheel"
  }
}

Input Schema

NameRequiredDescriptionDefault
notchesYes
instanceNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.6.0

TDQS

A4/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 full burden. It discloses that the action occurs at the current pointer position and explains the effect of positive/negative values. While it doesn't discuss side effects or prerequisites, the behavior is straightforward and clearly described.

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?

The description is two concise sentences that immediately convey the tool's purpose and key behavior. No wasted words, and the structure front-loads the core action.

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 simple input tool with two parameters and no output schema, the description covers the main operation and direction semantics. It lacks an explanation of the 'instance' parameter, but the default value and common usage across sibling tools mitigate this gap.

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?

The description explains the meaning of the 'notches' parameter (positive scrolls up, negative down), which is valuable given the 0% schema description coverage. However, it does not explain the 'instance' parameter, leaving one of two parameters undocumented.

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 clearly states the tool scrolls the mouse wheel at the current pointer position, with positive/negative values indicating direction. This distinguishes it from sibling tools like mouse_move and mouse_click.

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 description implies usage by explaining the action, but it does not provide explicit when-to-use guidance or mention alternative tools. No exclusions are given, but the context of when to scroll vs. click/move is only implicitly understood.

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