Skip to main content
Glama
MrGNSS

Desktop Commander MCP

by MrGNSS

unblock_command

Remove commands from the blacklist to restore normal execution functionality in the Desktop Commander MCP server.

Instructions

Remove a command from the blacklist. Once unblocked, the command can be executed normally.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
commandYes

Implementation Reference

  • Core handler function that removes the specified command from the blocked commands set and saves the updated list to the config file.
    async unblockCommand(command: string): Promise<boolean> {
      command = command.toLowerCase().trim();
      if (!this.blockedCommands.has(command)) {
        return false;
      }
      this.blockedCommands.delete(command);
      await this.saveBlockedCommands();
      return true;
    }
  • Dispatch handler in CallToolRequest that validates input args and delegates to commandManager.unblockCommand.
    case "unblock_command": {
      const parsed = UnblockCommandArgsSchema.parse(args);
      const unblockResult = await commandManager.unblockCommand(parsed.command);
      return {
        content: [{ type: "text", text: unblockResult }],
      };
    }
  • src/server.ts:108-113 (registration)
    Tool registration in ListToolsResponse, providing name, description, and input schema reference.
    {
      name: "unblock_command",
      description:
        "Remove a command from the blacklist. Once unblocked, the command can be executed normally.",
      inputSchema: zodToJsonSchema(UnblockCommandArgsSchema),
    },
  • Zod input schema validating the 'command' parameter as a string.
    export const UnblockCommandArgsSchema = z.object({
      command: z.string(),
    });

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
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 of behavioral disclosure. It states the action ('Remove') and outcome ('can be executed normally'), but lacks details on permissions required, whether the change is reversible, error handling (e.g., if command not in blacklist), or system effects. For a mutation tool with zero annotation coverage, this is insufficient.

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 two sentences that are front-loaded and efficient, with no wasted words. Each sentence adds value: the first states the action, and the second explains the consequence. It is appropriately sized for the tool's complexity.

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 mutation nature (removing from a blacklist), no annotations, no output schema, and low parameter coverage, the description is incomplete. It lacks critical details like permissions, error cases, or return values, making it inadequate for safe and effective use by an AI agent.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema has 1 parameter with 0% description coverage, and the description does not add any information about the 'command' parameter (e.g., format, examples, or what constitutes a valid command). It fails to compensate for the low schema coverage, leaving the parameter's meaning unclear beyond its name.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

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

The description clearly states the specific action ('Remove a command from the blacklist') and the resource ('a command'), distinguishing it from siblings like 'block_command' (which adds to blacklist) and 'list_blocked_commands' (which only reads). It also explains the outcome ('Once unblocked, the command can be executed normally'), making the purpose explicit and distinct.

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

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage when a command needs to be removed from a blacklist to allow execution, but it does not explicitly state when to use this tool versus alternatives (e.g., 'edit_block' might modify blacklist entries, or 'block_command' for adding). No exclusions or prerequisites are mentioned, leaving some ambiguity in context.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.