browser_mouse_wheel
Simulate mouse wheel scrolling in a browser page. Pass deltaX and deltaY to control horizontal and vertical scroll amounts.
Instructions
鼠标滚轮
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| deltaX | Yes | ||
| deltaY | Yes |
Simulate mouse wheel scrolling in a browser page. Pass deltaX and deltaY to control horizontal and vertical scroll amounts.
鼠标滚轮
| Name | Required | Description | Default |
|---|---|---|---|
| deltaX | Yes | ||
| deltaY | Yes |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, and the description gives no behavioral details. It does not disclose what effect the wheel action has, whether it scrolls horizontally/vertically, or any side effects. The burden falls entirely on the description, which is unmet.
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 extremely short (two Chinese characters), but this is under-specification rather than conciseness. It is not a complete sentence and conveys no meaningful information. It does not earn its place because it adds no value beyond the tool name.
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 two required parameters and no output schema, the description must clarify the tool's behavior and parameters. It does neither. The tool is a browser mouse wheel operation amidst many similar browser interaction tools, making the lack of context especially problematic.
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 two parameters (deltaX, deltaY) with 0% schema description coverage. The description does not explain what these deltas mean, how they relate to the wheel action, or expected ranges. It fails to compensate for the schema's lack of detail.
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 is simply '鼠标滚轮' (mouse wheel), a noun phrase that does not state any action or function. It fails to convey that this tool likely scrolls the mouse wheel, and it does not distinguish itself from sibling tools like browser_mouse_move or browser_scroll_to.
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?
There is no guidance on when to use this tool versus alternatives. The description offers no context, prerequisites, or exclusions, leaving the agent to guess at the intended use case.
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/91fapiao-cn/playwright-browser-skill'
If you have feedback or need assistance with the MCP directory API, please join our Discord server