skill_scroll_page
Scroll the connected machine's interface using PiKVM mouse scroll control.
Instructions
Guide for scrolling with pikvm_mouse_scroll
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Scroll the connected machine's interface using PiKVM mouse scroll control.
Guide for scrolling with pikvm_mouse_scroll
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations clearly indicate readOnlyHint=true and idempotentHint=true, implying no side effects. The description adds 'guide' which aligns with read-only behavior, but it does not provide additional behavioral context such as how scrolling is performed or what limits exist.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single short sentence, which is concise but at the expense of clarity. It lacks necessary detail to be useful on its own.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool has no parameters, no output schema, and a name suggesting a skill action, the description is incomplete. It does not explain what the tool does, how to use it, or its role among many similar siblings.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The input schema has zero parameters and 100% coverage, so the description need not explain parameters. However, the description fails to clarify the tool's core function, which is critical when no parameters are present.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description says 'Guide for scrolling with pikvm_mouse_scroll', but the tool name 'skill_scroll_page' implies it performs an action. It is unclear whether this is a meta-tool that provides guidance or actually executes scrolling. The verb 'guide' is ambiguous and does not clearly state the tool's function.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance is provided on when to use this tool versus siblings like 'pikvm_mouse_scroll' or other scroll-related skills. The description does not differentiate its purpose or specify prerequisites.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/KultivatorConsulting/pikvm_mcp_server'
If you have feedback or need assistance with the MCP directory API, please join our Discord server