Skip to main content
Glama

dap

Start a Debug Adapter Protocol server to connect debugging tools with the Delve debugger for analyzing Go programs.

Instructions

Start a DAP (Debug Adapter Protocol) server

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
clientAddrNoOptional address where DAP client is waiting for connection

Implementation Reference

  • The handler logic for the 'dap' tool, which starts a DAP debug session using startDebugSession with optional client address and returns a confirmation message.
    case "dap": {
      const { clientAddr } = args;
      const cmdArgs = clientAddr ? ["--client-addr", clientAddr] : [];
      
      const session = await startDebugSession("dap", "", cmdArgs);
      return {
        content: [{
          type: "text",
          text: `Started DAP server session ${session.id}${clientAddr ? ` connecting to ${clientAddr}` : ''}`
        }]
      };
    }
  • Input schema definition for the 'dap' tool, including optional 'clientAddr' parameter.
    {
      name: "dap",
      description: "Start a DAP (Debug Adapter Protocol) server",
      inputSchema: {
        type: "object",
        properties: {
          clientAddr: {
            type: "string",
            description: "Optional address where DAP client is waiting for connection"
          }
        }
      }
    },
  • src/server.ts:406-407 (registration)
    Dispatches calls to the 'dap' tool (and other debug tools) to the handleDebugCommands handler.
    if (["debug", "attach", "exec", "test", "core", "dap", "replay", "trace"].includes(name)) {
      return handleDebugCommands(name, args);
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. 'Start a DAP server' implies this initiates a debugging session, but it doesn't describe what happens after starting (e.g., does it run in background, block execution, require subsequent tools?), what permissions or prerequisites are needed, or what happens if a server is already running. For a tool that likely has significant behavioral implications, this is inadequate.

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, clear sentence with zero wasted words. It's appropriately sized for a tool with one optional parameter and gets straight to the point without unnecessary elaboration.

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 starting a debug adapter protocol server (which typically involves significant setup and interaction patterns), the lack of annotations, no output schema, and minimal description leaves major gaps. The agent won't understand what happens after starting the server, how to interact with it, or what the typical workflow should be with the many related sibling tools.

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?

The schema has 100% description coverage for its single parameter, so the schema already documents that 'clientAddr' is an 'Optional address where DAP client is waiting for connection.' The description adds no additional parameter information beyond what the schema provides, which meets the baseline expectation when schema coverage is complete.

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 action ('Start') and the resource ('a DAP server'), providing a specific verb+resource combination. However, it doesn't distinguish this tool from its many siblings (like 'debug', 'trace', 'test') that also relate to debugging operations, leaving some ambiguity about when to choose this specific tool.

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. With 17 sibling tools including 'debug', 'trace', and 'test' that might relate to debugging workflows, there's no indication of whether this should be used first, in combination with others, or as an alternative to specific 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