Skip to main content
Glama

shell_echo

Display text or output messages in shell environments using command arguments, enabling clear communication and debugging within secure command execution.

Instructions

Display text

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
argsNoCommand arguments

Implementation Reference

  • Configuration entry for 'shell.echo' tool mapping to shell 'echo' command with description and timeout settings.
    'shell.echo': {
      command: 'echo',
      description: 'Display text',
      timeout: 1000
    },
  • Dynamically generates MCP tool list from allowedCommands, creating an 'echo' tool (from 'shell.echo') with description and standard input schema.
    private processTools(): Tool[] {
      const tools: Tool[] = [];
      const processedNames = new Set<string>();
    
      this.logger.debug('Starting to process tool list', { 
        commandCount: Object.keys(allowedCommands).length 
      });
    
      Object.entries(allowedCommands).forEach(([name, config]) => {
        const toolName = name.replace('shell.', '');
        this.logger.debug('Processing command', { 
          originalName: name,
          toolName,
          isProcessed: processedNames.has(toolName)
        });
    
        if (!processedNames.has(toolName)) {
          processedNames.add(toolName);
          tools.push({
            name: toolName,
            description: config.description,
            inputSchema: {
              type: "object",
              properties: {
                args: {
                  type: "array",
                  items: { type: "string" },
                  description: "Command arguments"
                }
              }
            }
          });
        }
      });
    
      this.logger.debug('Tool list processing completed', { 
        toolCount: tools.length,
        processedNames: Array.from(processedNames)
      });
    
      this.validateToolNames(tools);
      return tools;
    }
  • Input schema definition for the 'echo' tool: object with 'args' property as array of strings.
    tools.push({
      name: toolName,
      description: config.description,
      inputSchema: {
        type: "object",
        properties: {
          args: {
            type: "array",
            items: { type: "string" },
            description: "Command arguments"
          }
        }
      }
    });
  • MCP CallTool request handler: for tool 'echo', constructs fullCommand 'shell.echo', retrieves config, validates args, executes via CommandExecutor, collects stdout and returns as text content.
      this.server.setRequestHandler(CallToolRequestSchema, async (request, extra: unknown) => {
        const ext = extra as Extra;
        if (!request.params?.name) {
          throw new ToolError('MISSING_COMMAND', 'Command name is required');
        }
        
        const command = String(request.params.name);
        const fullCommand = command.startsWith('shell.') ? command : `shell.${command}`;
        
        if (!(fullCommand in allowedCommands)) {
          throw new ToolError('COMMAND_NOT_FOUND', 'Command not found', { command });
        }
        
        const config = allowedCommands[fullCommand];
        const args = Array.isArray(request.params.arguments?.args)
          ? request.params.arguments.args.map(String)
          : [];
    
        const context: CommandContext = {
          requestId: ext.id || 'unknown',
          command,
          args,
          timeout: config.timeout,
          workDir: config.workDir,
          env: config.env
        };
    
        this.logger.info('Starting command execution', context);
    
        try {
          this.validator.validateCommand(command, args);
          
          this.logger.debug('Command validation passed', {
            ...context,
            config
          });
    
          const stream = await this.executor.execute(command, args, {
            timeout: config.timeout,
            cwd: config.workDir,
            env: config.env
          });
    
          ext.onCancel?.(() => {
            this.logger.info('Received cancel request', context);
            this.executor.interrupt();
          });
    
          const output = await this.collectOutput(stream);
    
          this.logger.info('Command execution completed', {
            ...context,
            outputLength: output.length
          });
    
          return {
            content: [{
              type: "text",
              text: output
            }]
          };
    
        } catch (error) {
          this.logger.error('Command execution failed', {
            ...context,
            error: error instanceof Error ? error.message : String(error),
            stack: error instanceof Error ? error.stack : undefined
          });
          
          throw new ToolError(
            'EXECUTION_FAILED',
            `Command execution failed: ${error instanceof Error ? error.message : String(error)}`,
            context
          );
        }
      });
    }
  • Core execution logic: spawns child_process for baseCommand='echo' (from command='echo'), handles security validation, caching, timeout, error handling, and returns stdout stream.
    async execute(
      command: string,
      args: string[] = [],
      options: ExecuteOptions = {}
    ): Promise<{ stdout: Readable }> {
      const commandKey = `${command} ${args.join(' ')}`;
      
      try {
        // Check security
        await this.securityChecker.validateCommand(command, args, options);
    
        // Check cache
        const cached = this.cache.get(commandKey);
        if (cached) {
          this.logger.debug('Using cached command result', { command, args });
          return this.createStreamFromCache(cached);
        }
    
        // Remove 'shell.' prefix for execution
        const baseCommand = command.replace('shell.', '');
    
        // Execute command
        this.logger.debug('Starting command execution', { command, args, options });
        const childProcess = spawn(baseCommand, args, {
          stdio: ['ignore', 'pipe', 'pipe'],
          timeout: options.timeout,
          cwd: options.cwd,
          env: {
            ...process.env,
            ...options.env
          },
          signal: options.signal
        });
    
        this.currentProcess = childProcess;
    
        // Error handling
        childProcess.on('error', (error: Error) => {
          this.logger.error('Command execution error', {
            command,
            args,
            error: error.message
          });
          throw new ToolError(
            'PROCESS_ERROR',
            'Command execution error',
            { command, args, error: error.message }
          );
        });
    
        // Timeout handling
        if (options.timeout) {
          setTimeout(() => {
            if (childProcess.exitCode === null) {
              this.logger.warn('Command execution timeout', {
                command,
                args,
                timeout: options.timeout
              });
              childProcess.kill();
              throw new ToolError(
                'TIMEOUT',
                'Command execution timeout',
                { command, args, timeout: options.timeout }
              );
            }
          }, options.timeout);
        }
    
        if (!childProcess.stdout) {
          throw new ToolError(
            'STREAM_ERROR',
            'Unable to get command output stream',
            { command, args }
          );
        }
    
        // Monitor process status
        childProcess.on('exit', (code, signal) => {
          this.logger.debug('Command execution completed', {
            command,
            args,
            exitCode: code,
            signal
          });
        });
    
        return {
          stdout: childProcess.stdout
        };
    
      } catch (error) {
        this.logger.error('Command execution failed', {
          command,
          args,
          error: error instanceof Error ? error.message : String(error)
        });
        
        throw new ToolError(
          'EXECUTION_ERROR',
          'Command execution failed',
          { 
            command, 
            args, 
            error: error instanceof Error ? error.message : String(error)
          }
        );
      }
    }
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries full burden but only states 'Display text' without disclosing behavioral traits like output format, side effects, or how it interacts with the shell. It's minimal and doesn't add meaningful context beyond the basic action.

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 two words, front-loaded and zero waste. It's appropriately sized for a simple tool, though this conciseness contributes to vagueness 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 no annotations, no output schema, and a simple tool, the description is incomplete. It doesn't explain what 'Display text' means in practice, return values, or how it fits with siblings, leaving gaps for agent understanding.

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%, so the schema documents the 'args' parameter well. The description adds no parameter semantics beyond what's in the schema, meeting the baseline for high coverage but not compensating with extra details.

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 'Display text' states a basic purpose (verb+action) but is vague about what 'text' refers to and doesn't distinguish from siblings like shell_cat or shell_echo. It's better than a tautology but lacks specificity about the shell echo command's exact function.

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 context, prerequisites, or comparisons to siblings like shell_cat for file output or shell_echo for command-line echoing, leaving usage unclear.

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/kevinwatt/shell-mcp'

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