Skip to main content
Glama

swipe

Perform scrollbar-semantic gestures in four directions to reveal off-screen content on live cloud device sessions, with short, medium, or long distance control.

Instructions

Perform a scrollbar-semantic swipe gesture in one of four directions.

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": {
      "direction": "<direction>"
    },
    "name": "swipe"
  }
}

Input Schema

NameRequiredDescriptionDefault
distanceNoSwipe distance: short, medium, or long (default: medium).
directionYesDirection to reveal content: up, down, left, or right.
session_idNoSession ID to target. Optional: falls back to the MCP-server-held dev_start session, then this project's `vibeview dev --detach` state, if either is available.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations only declare readOnlyHint=false, so the description adds the meaningful detail that the gesture reveals content in a given direction and defaults to a medium distance. It still says nothing about what happens at content boundaries, whether a device/session must be live, or failure behavior for an interaction tool.

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

Conciseness4/5

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

A single front-loaded sentence with no filler; the essential semantic qualifier appears before the parameter space is left to the schema. Appropriately sized for a simple gesture tool.

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

Completeness3/5

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

With full schema coverage, no output schema and a single required parameter, the description is minimally sufficient. It could still note prerequisites (active session/device) and behavior at scroll limits, which matter for an interaction tool whose annotations carry almost no safety context.

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?

Schema description coverage is 100%, so the schema already documents direction, distance values and the session_id fallback chain. The description contributes only the 'reveal content' framing of direction, which is marginal beyond that baseline.

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

Purpose4/5

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

States a specific verb (swipe gesture) plus a distinctive qualifier (scrollbar-semantic) and the direction axis, so an agent can distinguish it from scroll, scroll_to and drag. It does not explicitly name a sibling it replaces, which keeps it short of a 5.

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

Usage Guidelines2/5

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

No when-to-use or when-not-to-use guidance is given. The phrase 'scrollbar-semantic' hints that this moves a scrollbar rather than dragging content, but the description never says to prefer it over scroll/scroll_to/drag or when the alternative is appropriate.

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