Skip to main content
Glama
FutureAtoms

Agentic Control Framework (ACF)

by FutureAtoms

browser_drag

Drags browser elements from one location to another, enabling interactions with sliders, sortable lists, and draggable components.

Instructions

browser drag

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The main handler function browserDrag that executes drag-and-drop logic using Playwright's page.dragAndDrop() method. It accepts startElement, startRef, endElement, endRef parameters, validates refs, calls dragAndDrop with a timeout, and returns success/error response.
    /**
     * Drag and drop between elements
     */
    async function browserDrag(startElement, startRef, endElement, endRef) {
      try {
        if (!startRef || !endRef) {
          return {
            success: false,
            message: 'Both start and end element references are required'
          };
        }
    
        const page = await getPage();
        
        await page.dragAndDrop(startRef, endRef, {
          timeout: config.timeout
        });
    
        return {
          success: true,
          message: `Dragged from ${startElement} to ${endElement}`,
          startElement,
          startRef,
          endElement,
          endRef
        };
    
      } catch (error) {
        logger.error(`Error dragging: ${error.message}`);
        return {
          success: false,
          message: error.message
        };
      }
    }
  • The tools/call switch case that dispatches 'browser_drag' to the browserDrag function, passing args.startElement, args.startRef, args.endElement, args.endRef.
    case 'browser_drag': data = await browserTools.browserDrag(args.startElement, args.startRef, args.endElement, args.endRef); break;
  • Registration of 'browser_drag' tool in the browserExtras array within the tools/list handler, providing its name and auto-generated description.
    { n:'browser_navigate_back' }, { n:'browser_navigate_forward' }, { n:'browser_hover' }, { n:'browser_drag' },
  • Export of the browserDrag function from the browser_tools module, making it available for use in server.js.
    browserDrag,
Behavior1/5

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

No annotations are present, and the description does not disclose any behavioral traits (e.g., required coordinates, prerequisites, or effects). The tool's behavior remains entirely opaque.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

While extremely concise, the description is under-specification rather than efficient. It fails to provide necessary context that could be added in a few more words.

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

Completeness1/5

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

Given the simplicity of the tool (no parameters, no output schema, no annotations), the description is still critically incomplete. It omits any explanation of what dragging entails or how to execute it.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has 0 parameters, so the baseline is 4 per rules. The description adds no additional parameter information, but none is needed as there are no parameters to document.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'browser drag' is a tautology of the tool name, offering no additional clarity. It fails to distinguish this tool from siblings like browser_hover or browser_navigate.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No usage guidance is provided. The description does not indicate when to use this tool versus alternatives such as browser_hover or other browser interaction tools.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/FutureAtoms/agentic-control-framework'

If you have feedback or need assistance with the MCP directory API, please join our Discord server