Skip to main content
Glama
vdesabou

MCP Playground Server

by vdesabou

playground_command_help

Get detailed help for Kafka Docker Playground CLI commands to understand usage, parameters, and troubleshooting steps.

Instructions

Get detailed help for playground commands

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
commandYesCommand to get help for (e.g., 'connector restart', 'container logs')

Implementation Reference

  • The handler function for the 'playground_command_help' MCP tool. Extracts the 'command' argument, delegates to parser.getCommandHelp(), and returns the result formatted as MCP text content.
    private async handleCommandHelp(args: any) {
      const { command } = args;
      
      const help = this.parser.getCommandHelp(command);
      
      return {
        content: [
          {
            type: "text",
            text: JSON.stringify(help, null, 2),
          },
        ],
      };
    }
  • Input schema for the 'playground_command_help' tool, defining a required 'command' string parameter with description.
    inputSchema: {
      type: "object",
      properties: {
        command: {
          type: "string",
          description: "Command to get help for (e.g., 'connector restart', 'container logs')",
        },
      },
      required: ["command"],
    },
  • src/index.ts:102-103 (registration)
    Switch case in CallToolRequest handler that registers and routes calls to the 'playground_command_help' tool handler.
    case "playground_command_help":
      return await this.handleCommandHelp(args);
  • Primary helper implementing the help logic: splits command string, finds matching command via findCommand, assembles detailed help object with options, subcommands, examples, and generated usage.
    public getCommandHelp(commandString: string): any {
      const parts = commandString.trim().split(' ').filter(p => p.length > 0);
      
      // Remove 'playground' if it's the first part
      if (parts[0] === 'playground') {
        parts.shift();
      }
    
      const command = this.findCommand(parts);
      
      if (command) {
        return {
          command: parts.join(' '),
          description: command.description,
          options: command.options || [],
          subcommands: command.subcommands?.map(sub => ({
            name: sub.name,
            description: sub.description,
            options: sub.options || []
          })) || [],
          examples: command.examples || [],
          usage: this.generateUsage(command, parts.join(' '))
        };
      }
    
      return {
        error: 'Command not found',
        command: commandString
      };
    }
  • Supporting helper to locate a command or subcommand by path array, used by getCommandHelp.
    public findCommand(commandPath: string[]): PlaygroundCommand | null {
      let current = this.commands;
      let command: PlaygroundCommand | null = null;
    
      for (const part of commandPath) {
        command = current.find(cmd => cmd.name === part) || null;
        if (!command) return null;
        current = command.subcommands || [];
      }
    
      return command;
    }
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. While 'Get detailed help' implies a read-only operation, it doesn't specify whether this requires authentication, has rate limits, returns structured or unstructured data, or has any side effects. The description is too minimal for a mutation-free 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 a single, efficient sentence that communicates the core purpose without unnecessary words. It's appropriately sized for a simple tool and front-loads the essential information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple read-only tool with one well-documented parameter and no output schema, the description is minimally adequate but lacks important context. It doesn't explain what format the help returns (text, structured data), whether it covers all commands, or how it relates to sibling tools. The absence of annotations increases the need for more complete behavioral disclosure.

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 already fully documents the single 'command' parameter. The description doesn't add any additional meaning about parameter usage beyond what's in the schema (e.g., examples of valid commands beyond those shown). Baseline 3 is appropriate when schema does the heavy lifting.

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 tool's purpose with a specific verb ('Get') and resource ('detailed help for playground commands'), making it immediately understandable. However, it doesn't explicitly differentiate this from its sibling tools (playground_command_suggest and playground_command_validate), which would be needed for 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 its siblings (suggest and validate) or any alternative approaches. It simply states what the tool does without context about appropriate usage scenarios or exclusions.

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/vdesabou/kafka-docker-playground-mcp-server'

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