Skip to main content
Glama
allegiant

MQScript MCP Server

by allegiant

mqscript_device_vibrate

Control device vibration duration for mobile automation testing, feedback, or alerts using MQScript MCP Server's vibration function.

Instructions

Make device vibrate

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
durationNoVibration duration in milliseconds

Implementation Reference

  • Handler function that takes optional duration parameter and generates MQScript code to vibrate the device for that duration, returning a formatted text response.
    handler: async (args: { duration?: number }) => {
      const { duration = 200 } = args;
      const script = `Device.Vibrate(${duration})`;
      return {
        content: [
          {
            type: 'text',
            text: `Generated MQScript device vibrate command:\n\`\`\`\n${script}\n\`\`\`\n\nThis makes the device vibrate for ${duration} milliseconds.`
          }
        ]
      };
    }
  • Input schema for the tool, defining an optional 'duration' parameter (number, default 200ms).
    inputSchema: {
      type: 'object' as const,
      properties: {
        duration: {
          type: 'number',
          description: 'Vibration duration in milliseconds',
          default: 200
        }
      },
      required: []
    },
  • src/index.ts:53-53 (registration)
    The DeviceCommands object containing the 'mqscript_device_vibrate' tool is spread into the ALL_TOOLS registry used for tool lookup and execution.
    ...PhoneCommands,
Behavior2/5

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

With no annotations provided, the description carries full burden but only states the basic action. It doesn't disclose behavioral traits such as whether vibration requires specific permissions, if it's synchronous/asynchronous, potential side effects (e.g., interrupting other operations), or error conditions (e.g., unsupported devices). This leaves significant gaps 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 'Make device vibrate' is extremely concise with zero wasted words, front-loading the core action. It's appropriately sized for a simple tool, though this brevity contributes to gaps in other dimensions.

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 (vibration implies device change), the description is incomplete. It lacks details on behavior, return values, error handling, and device-specific constraints, making it inadequate for safe and effective use by an AI agent.

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%, with the 'duration' parameter fully documented in the schema as 'Vibration duration in milliseconds' with a default of 200. The description adds no additional meaning beyond the schema, so it meets the baseline of 3 where the schema does the heavy lifting.

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

Purpose3/5

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

The description 'Make device vibrate' clearly states the action (make vibrate) and target (device), but it's vague about scope and doesn't differentiate from siblings like 'mqscript_device_setbrightness' or 'mqscript_device_setvolume' which also affect device settings. It's functional but lacks specificity about what kind of vibration or device context.

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. It doesn't mention prerequisites (e.g., device compatibility), exclusions, or related tools like 'mqscript_device_getinfo' for checking device capabilities. The description alone offers no usage context.

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/allegiant/MQScript_MCP'

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