Skip to main content
Glama
allegiant

MQScript MCP Server

by allegiant

mqscript_dim

Define variables or arrays for mobile automation scripts to store and manage data during device control operations.

Instructions

Define variables or arrays

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
variablesYesVariable names separated by commas (e.g., "a, b(), c")

Implementation Reference

  • The handler function that generates an MQScript 'Dim' command for declaring variables and returns a textual response with the generated script.
    handler: async (args: { variables: string }) => {
      const { variables } = args;
      const script = `Dim ${variables}`;
      return {
        content: [
          {
            type: 'text',
            text: `Generated MQScript variable declaration:\n\`\`\`\n${script}\n\`\`\`\n\nThis declares variables: ${variables}.`
          }
        ]
      };
    }
  • The input schema validating the 'variables' parameter as a required string.
    inputSchema: {
      type: 'object' as const,
      properties: {
        variables: {
          type: 'string',
          description: 'Variable names separated by commas (e.g., "a, b(), c")'
        }
      },
      required: ['variables']
    },
  • The complete tool definition object within ControlCommands, including name 'mqscript_dim', description, inputSchema, and handler.
    dimVariable: {
      name: 'mqscript_dim',
      description: 'Define variables or arrays',
      inputSchema: {
        type: 'object' as const,
        properties: {
          variables: {
            type: 'string',
            description: 'Variable names separated by commas (e.g., "a, b(), c")'
          }
        },
        required: ['variables']
      },
      handler: async (args: { variables: string }) => {
        const { variables } = args;
        const script = `Dim ${variables}`;
        return {
          content: [
            {
              type: 'text',
              text: `Generated MQScript variable declaration:\n\`\`\`\n${script}\n\`\`\`\n\nThis declares variables: ${variables}.`
            }
          ]
        };
      }
    }
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. 'Define variables or arrays' implies a write/mutation operation, but it doesn't disclose behavioral traits like scope (local/global), persistence, error handling, or what happens if variables already exist. For a mutation tool with zero annotation coverage, this leaves critical behavioral aspects unspecified.

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 'Define variables or arrays' is extremely concise—just three words—with zero wasted language. It's front-loaded with the core action and resources. Every word earns its place by specifying both the operation and target, making it efficiently structured despite its brevity.

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 complexity of a variable/array definition tool with no annotations and no output schema, the description is incomplete. It doesn't explain the scripting context, return values, error conditions, or how this interacts with other tools in the mqscript_* family. For a mutation operation in what appears to be a scripting environment, more context is needed for 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 single parameter 'variables' documented as 'Variable names separated by commas (e.g., "a, b(), c")'. The description adds no additional meaning beyond this schema information, such as explaining what 'b()' signifies or how arrays are specified. With high schema coverage, the baseline score of 3 is appropriate.

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 'Define variables or arrays' clearly states the verb 'define' and the resources 'variables or arrays', providing a specific purpose. However, it doesn't distinguish this tool from its many siblings (e.g., mqscript_cint, mqscript_cstr) which also appear to define or convert values, leaving some ambiguity about when this particular definition tool should be used versus others.

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. With numerous sibling tools like mqscript_cint (convert to integer) and mqscript_cstr (convert to string), there's no indication whether this tool is for initial declaration, type conversion, or something else. No context, exclusions, or prerequisites are mentioned.

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