Skip to main content
Glama
allegiant

MQScript MCP Server

by allegiant

mqscript_device_getinfo

Retrieve specific device details such as model, brand, version, screen dimensions, or DPI for mobile automation scripting and device control.

Instructions

Get device information

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
infoTypeNoType of device info to getmodel
resultVariableNoVariable name to store resultdeviceInfo

Implementation Reference

  • Handler that destructures arguments, generates MQScript `Device.GetInfo` command string, and returns a formatted text response with the script.
    handler: async (args: { infoType?: string; resultVariable?: string }) => {
      const { infoType = 'model', resultVariable = 'deviceInfo' } = args;
      const script = `${resultVariable} = Device.GetInfo("${infoType}")`;
      return {
        content: [
          {
            type: 'text',
            text: `Generated MQScript get device info command:\n\`\`\`\n${script}\n\`\`\`\n\nThis gets device ${infoType} and stores it in variable "${resultVariable}".`
          }
        ]
      };
    }
  • Input schema defining optional infoType (enum: model, brand, etc.) and resultVariable parameters for the tool.
    inputSchema: {
      type: 'object' as const,
      properties: {
        infoType: {
          type: 'string',
          description: 'Type of device info to get',
          enum: ['model', 'brand', 'version', 'screenWidth', 'screenHeight', 'dpi'],
          default: 'model'
        },
        resultVariable: {
          type: 'string',
          description: 'Variable name to store result',
          default: 'deviceInfo'
        }
      },
      required: []
    },
  • src/index.ts:52-52 (registration)
    Spreading DeviceCommands into ALL_TOOLS object, which registers all tools including mqscript_device_getinfo for MCP server handling.
    ...DeviceCommands,
  • src/index.ts:15-15 (registration)
    Import of DeviceCommands containing the mqscript_device_getinfo tool definition.
    import { ElementCommands, DeviceCommands, PhoneCommands, SysCommands } from './tools/extension-commands.js';
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. 'Get device information' implies a read-only operation but doesn't specify if it requires permissions, has side effects, or how it handles errors. It lacks details on return format, rate limits, or any behavioral traits beyond the basic action.

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 extremely concise with a single phrase 'Get device information'. It is front-loaded and wastes no words, though this brevity comes at the cost of completeness. Every word serves a purpose, earning a high score for conciseness.

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?

For a tool with no annotations, no output schema, and 2 parameters, the description is incomplete. It doesn't explain what 'device information' entails, how results are returned, or any behavioral context. While the schema covers parameters, the overall tool purpose and usage remain under-specified.

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?

The schema description coverage is 100%, with both parameters ('infoType' and 'resultVariable') well-documented in the schema. The description adds no additional meaning beyond what the schema provides, such as examples or usage context. Given the 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.

Purpose2/5

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

The description 'Get device information' is a tautology that restates the tool name 'mqscript_device_getinfo' without adding specificity. It mentions the verb 'get' and resource 'device information' but doesn't distinguish what kind of device information or how it differs from sibling tools like 'mqscript_device_setbrightness' or 'mqscript_device_setvolume'.

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

Usage Guidelines1/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. The description doesn't mention any context, prerequisites, or exclusions, nor does it reference sibling tools for comparison. This leaves the agent with no usage direction.

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