Skip to main content
Glama

exec

Debug precompiled Go binaries by executing them with specified arguments to analyze and troubleshoot code behavior during runtime.

Instructions

Debug a precompiled binary

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
binaryYesPath to the binary
argsNoArguments to pass to the binary

Implementation Reference

  • Handler function for the 'exec' tool: parses binary path and args, starts a Delve debug session, and returns session info.
    case "exec": {
      const binary = String(args?.binary);
      const cmdArgs = (args?.args as string[]) || [];
    
      const session = await startDebugSession("exec", binary, cmdArgs);
      return {
        content: [{
          type: "text",
          text: `Started debug session ${session.id} for binary ${binary}`
        }]
      };
    }
  • Input schema definition for the 'exec' tool, specifying binary path (required) and optional arguments.
    {
      name: "exec",
      description: "Debug a precompiled binary",
      inputSchema: {
        type: "object",
        properties: {
          binary: {
            type: "string",
            description: "Path to the binary"
          },
          args: {
            type: "array",
            items: { type: "string" },
            description: "Arguments to pass to the binary"
          }
        },
        required: ["binary"]
      }
    },
  • src/server.ts:406-408 (registration)
    Registers and dispatches the 'exec' tool (among debug tools) to the handleDebugCommands function in CallToolRequest handler.
    if (["debug", "attach", "exec", "test", "core", "dap", "replay", "trace"].includes(name)) {
      return handleDebugCommands(name, args);
    }
  • Core helper function that implements the execution by spawning 'dlv exec --headless ... binary args' process and manages the debug session.
    export async function startDebugSession(type: string, target: string, args: string[] = []): Promise<DebugSession> {
      const port = await getAvailablePort();
      const id = Math.random().toString(36).substring(7);
      
      const dlvArgs = [
        type,
        "--headless",
        `--listen=:${port}`,
        "--accept-multiclient",
        "--api-version=2",
        target,
        ...args
      ];
    
      const process = spawn("dlv", dlvArgs, {
        stdio: ["pipe", "pipe", "pipe"]
      });
    
      const session: DebugSession = {
        id,
        type,
        target,
        process,
        port,
        breakpoints: new Map()
      };
    
      sessions.set(id, session);
      return session;
    }
  • Type definition including 'exec' for debug session types.
    type: string; // 'debug' | 'attach' | 'exec' | 'test' | 'core' | 'replay' | 'trace' | 'dap'
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. It mentions 'Debug' but doesn't clarify if this runs the binary, attaches to a process, requires specific permissions, has side effects like file modifications, or handles errors. This leaves critical behavioral traits undocumented.

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 quickly 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 debugging operations, no annotations, and no output schema, the description is incomplete. It lacks details on behavior, return values, error handling, and how it fits with sibling tools. For a tool that likely involves execution and interaction, more context is needed to guide effective use.

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 input schema has 100% description coverage, documenting 'binary' as a path and 'args' as arguments. The description adds no additional meaning beyond this, such as format examples or constraints. With high schema coverage, the baseline score of 3 is appropriate as the schema handles parameter documentation adequately.

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 'Debug a precompiled binary' states a clear verb ('Debug') and resource ('precompiled binary'), but it's vague about what debugging entails—whether it's running, stepping, or analyzing. It doesn't differentiate from siblings like 'debug' (which might be similar) or 'step' (which could be a specific action), leaving ambiguity in its exact function.

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 like 'debug', 'step', or 'trace'. The description implies a general debugging action but doesn't specify contexts, prerequisites, or exclusions, such as whether it's for initial execution or ongoing debugging sessions.

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