Skip to main content
Glama
MrGNSS

Desktop Commander MCP

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(),
    });
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. It states the tool removes a command from the blacklist and allows execution, but does not disclose behavioral traits such as permissions required, whether the change is permanent or reversible, error conditions, or rate limits. This is a significant gap for a mutation tool with zero annotation coverage.

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, front-loaded with the core action, and every sentence earns its place by explaining the purpose and outcome without waste. 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 complexity (a mutation operation with no annotations, no output schema, and 0% schema coverage), the description is incomplete. It lacks details on parameter semantics, behavioral traits, error handling, and output expectations, 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 description coverage is 0%, with one undocumented parameter ('command'). The description does not add any meaning beyond what the schema provides—it mentions 'command' but does not explain what constitutes a valid command, format requirements, or examples. It fails to compensate for the low schema coverage.

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 affected ('command'), with the outcome ('Once unblocked, the command can be executed normally'). It distinguishes from its sibling 'block_command' by being the inverse operation.

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

Usage Guidelines4/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 the blacklist to allow execution, but does not explicitly state when to use this tool versus alternatives like 'edit_block' or 'list_blocked_commands'. It provides clear context but lacks explicit exclusions or named alternatives.

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/MrGNSS/ClaudeDesktopCommander'

If you have feedback or need assistance with the MCP directory API, please join our Discord server