Skip to main content
Glama
allegiant

MQScript MCP Server

by allegiant

mqscript_file_delete

Remove files from mobile devices during automation to manage storage and clean up temporary data generated by MQScript mobile automation processes.

Instructions

Delete file

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
filePathYesFile path to delete

Implementation Reference

  • The async handler function that implements the core logic of the mqscript_file_delete tool. It receives the filePath argument, constructs an MQScript 'File.Delete' command string, and returns a formatted text response describing the generated script.
    handler: async (args: { filePath: string }) => {
      const { filePath } = args;
      const script = `File.Delete("${filePath}")`;
      return {
        content: [
          {
            type: 'text',
            text: `Generated MQScript file delete command:\n\`\`\`\n${script}\n\`\`\`\n\nThis deletes file "${filePath}".`
          }
        ]
      };
    }
  • The inputSchema defining the structure and requirements for the tool's arguments, specifying that 'filePath' (string) is required.
    inputSchema: {
      type: 'object' as const,
      properties: {
        filePath: {
          type: 'string',
          description: 'File path to delete'
        }
      },
      required: ['filePath']
    },
  • The complete definition of the mqscript_file_delete tool object (including name, description, schema, and handler), which is exported as part of FileCommands and spread into the global ALL_TOOLS registry for MCP server registration.
    delete: {
      name: 'mqscript_file_delete',
      description: 'Delete file',
      inputSchema: {
        type: 'object' as const,
        properties: {
          filePath: {
            type: 'string',
            description: 'File path to delete'
          }
        },
        required: ['filePath']
      },
      handler: async (args: { filePath: string }) => {
        const { filePath } = args;
        const script = `File.Delete("${filePath}")`;
        return {
          content: [
            {
              type: 'text',
              text: `Generated MQScript file delete command:\n\`\`\`\n${script}\n\`\`\`\n\nThis deletes file "${filePath}".`
            }
          ]
        };
      }
    },
  • src/index.ts:57-60 (registration)
    The spreading of FileCommands (containing mqscript_file_delete) into the ALL_TOOLS object used by the MCP server for tool listing and execution.
    ...CJsonCommands,
    ...DateTimeCommands,
    ...FileCommands,
    ...TuringCommands,
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. 'Delete file' implies a destructive mutation, but it doesn't disclose critical behaviors: whether deletion is permanent or reversible, permission requirements, error handling (e.g., if file doesn't exist), or side effects. This leaves significant gaps for a destructive operation.

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 just two words, front-loading the essential action. There is no wasted language, making it efficient for quick understanding, 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 the tool's destructive nature, no annotations, and no output schema, the description is incomplete. It lacks details on behavior, outcomes, error cases, and usage context, which are crucial for safe and effective tool invocation 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?

The schema description coverage is 100%, with the parameter 'filePath' clearly documented as 'File path to delete'. The description adds no additional meaning beyond this, but since the schema is comprehensive, the baseline score of 3 is appropriate as it doesn't need to compensate.

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 'Delete file' clearly states the action (delete) and resource (file), but it's vague about scope and lacks differentiation from siblings like 'mqscript_file_copy' or 'mqscript_file_write'. It doesn't specify if it deletes a single file, multiple files, or has any constraints.

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., file must exist), when not to use it (e.g., for directories), or compare it to sibling file operations like 'mqscript_file_copy' for moving files.

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