Skip to main content
Glama
MrGNSS

Desktop Commander MCP

list_blocked_commands

View all currently blocked terminal commands in the Desktop Commander MCP server to maintain security and control over system operations.

Instructions

List all currently blocked commands.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • MCP tool handler for 'list_blocked_commands' that calls commandManager.listBlockedCommands() and returns the sorted list of blocked commands as newline-separated text.
    case "list_blocked_commands": {
      const blockedCommands = await commandManager.listBlockedCommands();
      return {
        content: [{ type: "text", text: blockedCommands.join('\n') }],
      };
    }
  • src/server.ts:114-123 (registration)
    Registration of the 'list_blocked_commands' tool in the server.ListToolsRequestHandler response, including name, description, and empty input schema (no parameters required).
    {
      name: "list_blocked_commands",
      description:
        "List all currently blocked commands.",
      inputSchema: {
        type: "object",
        properties: {},
        required: [],
      },
    },
  • Helper method in CommandManager class that returns the sorted array of currently blocked commands from the internal Set.
    listBlockedCommands(): string[] {
      return Array.from(this.blockedCommands).sort();
    }
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. It states the action ('List') but doesn't describe what 'blocked commands' entails (e.g., system-level vs. user-level), how results are returned (e.g., format, pagination), or any side effects. This leaves significant gaps for a tool that likely involves security or system state.

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 a single, efficient sentence that directly states the tool's function without unnecessary words. It's front-loaded with the core action and resource, making it easy to parse quickly.

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 complexity of listing system commands (likely involving security or permissions) and the absence of annotations and output schema, the description is insufficient. It doesn't explain what 'blocked commands' means, how results are structured, or any behavioral nuances, leaving the agent with incomplete context for effective use.

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

Parameters4/5

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

The input schema has 0 parameters with 100% coverage, so no parameter documentation is needed. The description doesn't add parameter details, which is appropriate, but it could have mentioned implicit constraints (e.g., no filtering options). Baseline is 4 for zero-parameter tools, as there's nothing to compensate for.

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

Purpose4/5

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

The description clearly states the verb ('List') and resource ('blocked commands') with the scope 'all currently', making the purpose unambiguous. However, it doesn't explicitly differentiate from sibling tools like 'list_allowed_directories' or 'list_processes' beyond the resource name, which prevents a perfect score.

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?

The description provides no guidance on when to use this tool versus alternatives, such as 'unblock_command' for managing blocked commands or other list tools for different resources. It lacks context about prerequisites or typical use cases, offering only a basic functional statement.

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