Skip to main content
Glama
allegiant

MQScript MCP Server

by allegiant

mqscript_delay

Pause mobile automation script execution for a specified duration in milliseconds to control timing between operations.

Instructions

Pause script execution for specified duration

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
millisecondsYesDelay duration in milliseconds

Implementation Reference

  • The handler function that executes the tool logic, generating an MQScript 'Delay' command based on the provided milliseconds and returning a formatted response.
    handler: async (args: { milliseconds: number }) => {
      const { milliseconds } = args;
      const script = `Delay ${milliseconds}`;
      return {
        content: [
          {
            type: 'text',
            text: `Generated MQScript delay command:\n\`\`\`\n${script}\n\`\`\`\n\nThis will pause execution for ${milliseconds}ms (${milliseconds/1000} seconds).`
          }
        ]
      };
    }
  • The input schema defining the tool's parameters: a required 'milliseconds' number.
    inputSchema: {
      type: 'object' as const,
      properties: {
        milliseconds: {
          type: 'number',
          description: 'Delay duration in milliseconds'
        }
      },
      required: ['milliseconds']
    },
  • The tool registration within ControlCommands object, defining name, description, schema, and handler. This object is spread into the ALL_TOOLS registry in src/index.ts.
    delay: {
      name: 'mqscript_delay',
      description: 'Pause script execution for specified duration',
      inputSchema: {
        type: 'object' as const,
        properties: {
          milliseconds: {
            type: 'number',
            description: 'Delay duration in milliseconds'
          }
        },
        required: ['milliseconds']
      },
      handler: async (args: { milliseconds: number }) => {
        const { milliseconds } = args;
        const script = `Delay ${milliseconds}`;
        return {
          content: [
            {
              type: 'text',
              text: `Generated MQScript delay command:\n\`\`\`\n${script}\n\`\`\`\n\nThis will pause execution for ${milliseconds}ms (${milliseconds/1000} seconds).`
            }
          ]
        };
      }
    },
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It states the tool pauses execution, implying it's a blocking operation, but doesn't disclose behavioral traits such as whether it's interruptible, if it affects script state, error handling for invalid durations, or performance impacts. The description is minimal and lacks necessary context for safe use.

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 that front-loads the core action ('Pause script execution') and specifies the key detail ('for specified duration'). There is zero waste, and every word earns its place, making it easy to parse quickly.

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 the tool's complexity (a blocking delay operation with no annotations and no output schema), the description is incomplete. It lacks information on behavioral risks (e.g., script hanging), error conditions, or return values. For a tool that could significantly impact script flow, more context is needed to ensure safe and effective use.

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 parameter 'milliseconds' clearly documented in the schema. The description adds no additional meaning beyond implying a duration is specified, which is already covered. With high schema coverage, the baseline score of 3 is appropriate, as the description doesn't compensate but doesn't detract either.

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 clearly states the verb ('Pause') and resource ('script execution') with the specific action of delaying for a specified duration. It distinguishes itself from siblings by focusing on timing control rather than UI manipulation, file operations, or other script functions, though it doesn't explicitly contrast with similar timing tools like 'mqscript_sys_sleep'.

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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention sibling tools like 'mqscript_sys_sleep' (which might serve a similar purpose) or specify contexts where a delay is appropriate (e.g., waiting for UI updates, network responses). Usage is implied only through the action described.

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