Skip to main content
Glama

configureLogging

Enable logging for selected Delve debug components and specify the destination for log output.

Instructions

Configure debug logging

Input Schema

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

Implementation Reference

  • Handler function for configureLogging that validates logging components, sets environment variables DELVE_LOG, DELVE_LOG_OUTPUT, and optionally DELVE_LOG_DEST.
    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 definition for configureLogging tool: requires components array (with enum validation) 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)
    Routes configureLogging tool calls to handleConfigCommands in the CallToolRequestSchema handler.
    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?

With no annotations, the description carries the full burden. It does not disclose whether the configuration is additive or overriding, persists across sessions, or requires any special conditions. This is a significant gap for a configuration tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely concise at one sentence, but this verges on underspecification. It does not front-load key details or structure information for quick consumption.

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 simplicity of the tool (no output schema, flat parameters), the description could still be more complete. It fails to explain the effect of configuring logging, such as whether existing logs are affected or if there are side effects.

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 coverage is 100% with descriptions for both parameters ('components' and 'destination'). The tool description adds no extra meaning beyond what the schema already provides, so baseline score of 3 is appropriate.

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 'Configure debug logging' clearly states the action and resource, distinguishing this from sibling tools like attach, continue, and evaluate which are debugger commands. However, it lacks specificity about what logging configuration entails.

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 explicit guidance is provided on when to use this tool versus alternatives, nor are any prerequisites or contextual constraints mentioned. The agent must infer usage solely from the tool name and siblings.

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