Skip to main content
Glama

debug_mcp_config

Analyze and troubleshoot the current MCP configuration on the mcp-with-ssh server. Optionally include detailed insights by enabling verbose mode.

Instructions

Debug the current MCP configuration

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
verboseNoWhether to include detailed information

Implementation Reference

  • The handler function that executes the debug_mcp_config tool, gathering and returning detailed MCP configuration information including memory bank status, mode info, and system details.
    export async function handleDebugMcpConfig(
      memoryBankManager: MemoryBankManager,
      verbose: boolean = false
    ) {
      try {
        // Get basic information
        const memoryBankDir = memoryBankManager.getMemoryBankDir();
        const projectPath = memoryBankManager.getProjectPath();
        const language = memoryBankManager.getLanguage();
        const folderName = memoryBankManager.getFolderName();
        
        // Get mode information
        const modeManager = memoryBankManager.getModeManager();
        let modeInfo = null;
        if (modeManager) {
          const currentModeState = modeManager.getCurrentModeState();
          modeInfo = {
            name: currentModeState.name,
            isUmbActive: currentModeState.isUmbActive,
            memoryBankStatus: currentModeState.memoryBankStatus
          };
        }
        
        // Get Memory Bank status
        let memoryBankStatus = null;
        try {
          if (memoryBankDir) {
            memoryBankStatus = await memoryBankManager.getStatus();
          }
        } catch (error) {
          console.error('Error getting Memory Bank status:', error);
        }
        
        // Get system information
        const systemInfo = {
          platform: os.platform(),
          release: os.release(),
          arch: os.arch(),
          nodeVersion: process.version,
          cwd: process.cwd(),
          env: verbose ? process.env : undefined
        };
        
        // Collect all information
        const debugInfo = {
          timestamp: new Date().toISOString(),
          memoryBank: {
            directory: memoryBankDir,
            projectPath,
            language,
            folderName,
            status: memoryBankStatus
          },
          mode: modeInfo,
          system: systemInfo
        };
        
        return {
          content: [
            {
              type: "text",
              text: `MCP Configuration Debug Information:\n${JSON.stringify(debugInfo, null, 2)}`,
            },
          ],
        };
      } catch (error) {
        console.error("Error in handleDebugMcpConfig:", error);
        return {
          content: [
            {
              type: "text",
              text: `Error debugging MCP configuration: ${error}`,
            },
          ],
          isError: true
        };
      }
    }
  • The input schema and tool definition for debug_mcp_config, part of the coreTools array used for tool registration and validation.
    {
      name: 'debug_mcp_config',
      description: 'Debug the current MCP configuration',
      inputSchema: {
        type: 'object',
        properties: {
          verbose: {
            type: 'boolean',
            description: 'Whether to include detailed information',
            default: false,
          },
        },
        required: [],
      },
    },
  • The switch case in the tool call handler that registers and routes 'debug_mcp_config' requests to the handleDebugMcpConfig function.
    case 'debug_mcp_config': {
      const { verbose } = request.params.arguments as { verbose?: boolean };
      return handleDebugMcpConfig(memoryBankManager, verbose || false);
    }
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. 'Debug' implies a read-only or diagnostic operation, but the description doesn't clarify if it's safe, what it outputs, or if it has side effects like logging or configuration changes. For a tool with zero annotation coverage, this is a significant gap in transparency.

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 with no wasted words. It's front-loaded and directly states the tool's purpose, making it easy to parse. Every word earns its place, achieving optimal conciseness for such a simple tool.

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 lack of annotations and output schema, the description is incomplete. It doesn't explain what debugging outputs (e.g., configuration details, errors), how it behaves, or its role among sibling tools. For a tool in a complex server with many siblings, this minimal description leaves critical context gaps.

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 1 parameter with 100% description coverage, so the schema fully documents the 'verbose' parameter. The description adds no parameter information beyond the schema, but with high schema coverage and only one optional parameter, the baseline is high. A score of 4 reflects that the schema handles parameter semantics adequately, though the description doesn't enhance it.

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 states the tool's purpose ('Debug the current MCP configuration'), which is clear but vague. It specifies the verb ('Debug') and resource ('MCP configuration'), but doesn't explain what debugging entails or how it differs from sibling tools like 'get_current_mode' or 'switch_mode'. The purpose is understandable but lacks specificity.

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. It doesn't mention any prerequisites, context, or exclusions, nor does it reference sibling tools. Without usage guidelines, an agent must infer when debugging is appropriate, which could lead to misuse.

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

Related 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/aakarsh-sasi/memory-bank-mcp'

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