Skip to main content
Glama
allegiant

MQScript MCP Server

by allegiant

mqscript_datetime_compare

Compare two DateTime variables in mobile automation scripts to determine temporal relationships and store results for conditional logic.

Instructions

Compare two date times

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dateTime1YesFirst DateTime variable name
dateTime2YesSecond DateTime variable name
resultVariableNoVariable name to store comparison resultcompareResult

Implementation Reference

  • The handler function that implements the core logic of the mqscript_datetime_compare tool by generating the corresponding MQScript DateTime.Compare command.
    handler: async (args: { dateTime1: string; dateTime2: string; resultVariable?: string }) => {
      const { dateTime1, dateTime2, resultVariable = 'compareResult' } = args;
      const script = `${resultVariable} = DateTime.Compare(${dateTime1}, ${dateTime2})`;
      return {
        content: [
          {
            type: 'text',
            text: `Generated MQScript DateTime compare command:\n\`\`\`\n${script}\n\`\`\`\n\nThis compares "${dateTime1}" with "${dateTime2}" and stores result in "${resultVariable}".`
          }
        ]
      };
    }
  • The input schema defining the parameters for the mqscript_datetime_compare tool: dateTime1, dateTime2 (required), and optional resultVariable.
    inputSchema: {
      type: 'object' as const,
      properties: {
        dateTime1: {
          type: 'string',
          description: 'First DateTime variable name'
        },
        dateTime2: {
          type: 'string',
          description: 'Second DateTime variable name'
        },
        resultVariable: {
          type: 'string',
          description: 'Variable name to store comparison result',
          default: 'compareResult'
        }
      },
      required: ['dateTime1', 'dateTime2']
    },
  • The tool definition and registration within DateTimeCommands object, which is later spread into the main ALL_TOOLS registry.
    compare: {
      name: 'mqscript_datetime_compare',
      description: 'Compare two date times',
      inputSchema: {
        type: 'object' as const,
        properties: {
          dateTime1: {
            type: 'string',
            description: 'First DateTime variable name'
          },
          dateTime2: {
            type: 'string',
            description: 'Second DateTime variable name'
          },
          resultVariable: {
            type: 'string',
            description: 'Variable name to store comparison result',
            default: 'compareResult'
          }
        },
        required: ['dateTime1', 'dateTime2']
      },
      handler: async (args: { dateTime1: string; dateTime2: string; resultVariable?: string }) => {
        const { dateTime1, dateTime2, resultVariable = 'compareResult' } = args;
        const script = `${resultVariable} = DateTime.Compare(${dateTime1}, ${dateTime2})`;
        return {
          content: [
            {
              type: 'text',
              text: `Generated MQScript DateTime compare command:\n\`\`\`\n${script}\n\`\`\`\n\nThis compares "${dateTime1}" with "${dateTime2}" and stores result in "${resultVariable}".`
            }
          ]
        };
      }
    }
  • src/index.ts:56-58 (registration)
    Spreading DateTimeCommands (containing mqscript_datetime_compare) into the main ALL_TOOLS object used for tool listing and execution.
    // Plugin Commands - 插件命令
    ...CJsonCommands,
    ...DateTimeCommands,
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 'Compare two date times' but doesn't disclose behavioral traits like what the comparison returns (e.g., boolean, integer difference), side effects (e.g., stores result in a variable), or error handling. This is inadequate for a tool with potential mutation (storing results).

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 ('Compare two date times') with zero wasted words, making it front-loaded and easy to parse. However, this conciseness comes at the cost of completeness, but for this dimension alone, it's optimal.

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 and no output schema, the description is incomplete. It doesn't explain what the comparison does (e.g., returns -1, 0, 1 for ordering), how results are stored or used, or error cases. For a tool with 3 parameters and potential behavioral complexity, this is insufficient.

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 clear parameter descriptions in the schema (e.g., 'First DateTime variable name'). The description adds no additional meaning beyond the schema, but since the schema is comprehensive, the baseline score of 3 is appropriate as it doesn't detract value.

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 'Compare two date times' clearly states the verb (compare) and resource (date times), but it's vague about what comparison means (e.g., equality, ordering, difference) and doesn't distinguish from siblings like 'mqscript_datetime_adddays' or 'mqscript_datetime_format'. It's adequate but lacks specificity.

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 on when to use this tool versus alternatives is provided. The description doesn't mention prerequisites, context, or exclusions, leaving the agent to infer usage based on the name alone. This is a significant gap for a tool in a set with many datetime-related siblings.

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