Skip to main content
Glama

configureLogging

Set up debug logging for specific components in Delve MCP to monitor and troubleshoot Go program debugging sessions.

Instructions

Configure debug logging

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
componentsYesComponents to enable logging for
destinationNoLog destination (file path or file descriptor)

Implementation Reference

  • Handler logic for the 'configureLogging' tool within handleConfigCommands function. Validates components, sets DELVE_LOG environment variables, and returns confirmation message.
    case "configureLogging": {
      const { components, destination } = args;
      const validComponents = ["debugger", "gdbwire", "lldbout", "debuglineerr", "rpc", "dap", "fncall", "minidump", "stack"];
      
      for (const component of components) {
        if (!validComponents.includes(component)) {
          throw new Error(`Invalid log component: ${component}`);
        }
      }
    
      process.env.DELVE_LOG = "1";
      process.env.DELVE_LOG_OUTPUT = components.join(",");
      if (destination) {
        process.env.DELVE_LOG_DEST = destination;
      }
    
      return {
        content: [{
          type: "text",
          text: `Configured logging for components: ${components.join(", ")}`
        }]
      };
    }
  • Input schema for 'configureLogging' tool, defining required 'components' array with valid enums and optional 'destination' string.
      name: "configureLogging",
      description: "Configure debug logging",
      inputSchema: {
        type: "object",
        properties: {
          components: {
            type: "array",
            items: {
              type: "string",
              enum: ["debugger", "gdbwire", "lldbout", "debuglineerr", "rpc", "dap", "fncall", "minidump", "stack"]
            },
            description: "Components to enable logging for"
          },
          destination: {
            type: "string",
            description: "Log destination (file path or file descriptor)"
          }
        },
        required: ["components"]
      }
    }
  • src/server.ts:416-418 (registration)
    Registration/dispatch in CallToolRequestSchema handler that routes 'configureLogging' tool calls to the handleConfigCommands function.
    if (["setBackend", "configureLogging", "version"].includes(name)) {
      return handleConfigCommands(name, args);
    }
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. 'Configure debug logging' implies a mutation (changing logging settings), but it does not disclose behavioral traits such as permissions needed, whether changes are persistent, side effects, or error handling. This is inadequate 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 a single, efficient phrase with no wasted words. It is appropriately sized and front-loaded, making it easy to parse quickly, though it lacks detail.

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 a mutation tool with no annotations and no output schema, the description is incomplete. It does not explain what 'configure' does (e.g., enable/disable), the scope of changes, or return values, leaving significant gaps for the agent to understand the tool's behavior.

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 documents both parameters ('components' and 'destination') with descriptions and an enum for 'components'. The description adds no meaning beyond the schema, such as explaining how components interact or what 'configure' entails for these parameters, meeting the baseline for high schema coverage.

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 'Configure debug logging' states the verb ('configure') and resource ('debug logging'), but is vague about what configuration entails—whether it enables, disables, or modifies logging. It does not distinguish from siblings like 'debug' or 'trace', which might relate to logging or debugging functions.

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 is provided on when to use this tool versus alternatives. It does not mention prerequisites, context (e.g., during debugging sessions), or exclusions, leaving the agent to infer usage from the tool name alone among many sibling tools.

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/dwisiswant0/delve-mcp'

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