Skip to main content
Glama

shake

Triggers a single motion gesture on connected phones, tablets, or foldables so you can verify device-motion interactions during live app testing.

Instructions

Shake the device once (phones, tablets and foldables)

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "shake"
  }
}

Input Schema

NameRequiredDescriptionDefault
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.3/5.0
Behavior2/5

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

Annotations only supply readOnlyHint=false; the description adds nothing beyond noting the gesture fires 'once'. It does not say whether this injects a motion event, how long it lasts, whether the device must be in a particular state, or what visible effect follows, which matters for a state-changing input tool.

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

Conciseness5/5

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

One short front-loaded sentence with the action first and the device-scope qualifier in parentheses. Nothing redundant or padded.

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?

For a very simple zero-required-parameter gesture tool this is roughly adequate, especially since the schema explains session targeting. It still leaves the agent without confirmation of side effects or preconditions, which are the main open questions for an input-injection tool.

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 coverage is 100% and includes the session_id fallback chain, so the description contributes no additional parameter meaning. Baseline 3 applies when the schema fully documents the single optional parameter.

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 ('Shake') and resource ('the device') plus scope ('phones, tablets and foldables'), so an agent knows exactly what gesture is simulated. It doesn't distinguish itself from gesture/posture siblings like rotate or set_posture, but the action noun is unambiguous.

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

Usage Guidelines3/5

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

Usage is implied by the gesture name and the device-type parenthetical, but there is no explicit when-to-use guidance, no mention of prerequisites (e.g. an active session or connected device), and no routing to alternatives such as rotate or set_posture.

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