Execute human-like drag actions for sliders, reordering, or canvas drawing by moving from one element or coordinates to another with realistic path and mouse hold.
Perform a human-like drag from one element/ref or coords to another (e.g. for sliders, reordering, canvas drawing). Uses the realistic path engine while holding the mouse button.
| Name | Required | Description | Default |
|---|---|---|---|
| toX | No | ||
| toY | No | ||
| fromX | No | ||
| fromY | No | ||
| toRef | No | ||
| button | No | ||
| fromRef | No | ||
| stealth | No |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations, so description carries full burden. Discloses 'human-like drag', 'realistic path engine', and 'holding mouse button', giving insight into behavior. Could mention whether it waits for completion or supports cancellation.
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?
Two sentences, front-loaded with main purpose, then behavioral detail. No redundant or unnecessary words. Efficient.
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?
With 8 parameters, 0% schema coverage, no output schema, and no annotations, the description is too brief. Does not cover parameter roles or output format. Needs more detail for a complex interaction tool.
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?
Schema description coverage is 0%, and description does not explain any of the 8 parameters. Parameter names (toX, fromY, button, stealth, etc.) are somewhat self-explanatory, but lack of clarity on 'stealth' and 'toRef' vs coordinates reduces utility.
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?
Description clearly states verb 'drag' with specific resources (elements/refs/coords) and provides examples (sliders, reordering, canvas drawing). Distinguishes from sibling tools like click, move_to, hover.
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?
Provides context with examples (e.g. sliders, reordering, canvas drawing) implicitly guiding when to use. Lacks explicit when-not-to-use or alternatives, but context is sufficient for typical choices.
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/kumard3/agentcursor'
If you have feedback or need assistance with the MCP directory API, please join our Discord server