Skip to main content
Glama
Sign In
AutoMobile

AutoMobile

by zillow
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

shake

Simulate device shaking for mobile testing on Android or iOS platforms, controlling duration and intensity parameters for automation scenarios.

Instructions

Shake the device

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": {
      "platform": "<platform>"
    },
    "name": "shake"
  }
}

Input Schema

NameRequiredDescriptionDefault
durationNoDuration of the shake in milliseconds (default: 1000)
intensityNoIntensity of the shake acceleration (default: 100)
platformYesPlatform of the device

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries full burden. It states the action but doesn't disclose behavioral traits like whether this requires specific permissions, if it's safe/reversible, what happens to the device state, or any side effects (e.g., interrupting apps). This is a significant gap for a mutation 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?

The description is a single, efficient sentence with zero waste. It's appropriately sized and front-loaded, making it easy to parse without unnecessary elaboration.

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

Completeness2/5

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

Given no annotations, no output schema, and a mutation tool with 3 parameters, the description is incomplete. It lacks behavioral context, usage guidelines, and details on effects, leaving gaps for an agent to understand when and how to invoke it safely.

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 all parameters (duration, intensity, platform) with descriptions and defaults. The description adds no parameter semantics beyond what the schema provides, meeting the baseline for high coverage.

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?

The description 'Shake the device' clearly states the action (shake) and target (device) with a specific verb+resource. However, it doesn't differentiate from sibling tools like 'swipe' or 'rotate' that also manipulate device orientation/motion, missing explicit distinction.

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 guidance is provided on when to use this tool versus alternatives (e.g., 'swipe' or 'rotate' for other motions) or in what context (e.g., testing, simulation). The description lacks any usage context or exclusions.

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

Deploy Server

Other Tools