Skip to main content
Glama

setBackend

Configure the debugging backend for Go programs by selecting from available options like default, native, lldb, or rr to enable code analysis and troubleshooting.

Instructions

Set the backend for debugging

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
backendYesBackend to use (default, native, lldb, or rr)

Implementation Reference

  • Executes the setBackend tool: validates the backend (default, native, lldb, rr), sets DELVE_BACKEND env var, and returns confirmation message.
    case "setBackend": {
      const { backend } = args;
      if (!["default", "native", "lldb", "rr"].includes(backend)) {
        throw new Error("Invalid backend specified");
      }
    
      process.env.DELVE_BACKEND = backend;
      return {
        content: [{
          type: "text",
          text: `Set Delve backend to ${backend}`
        }]
      };
    }
  • Input schema definition for setBackend tool in ListTools response, requiring 'backend' with specific enum values.
      name: "setBackend",
      description: "Set the backend for debugging",
      inputSchema: {
        type: "object",
        properties: {
          backend: {
            type: "string",
            description: "Backend to use (default, native, lldb, or rr)",
            enum: ["default", "native", "lldb", "rr"]
          }
        },
        required: ["backend"]
      }
    },
  • src/server.ts:416-418 (registration)
    In CallToolRequest handler, routes 'setBackend' 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 of behavioral disclosure. It states the tool sets a backend for debugging, implying a configuration change, but doesn't disclose whether this requires specific permissions, if changes are persistent, what happens to ongoing debugging sessions, or any rate limits. The description is minimal and lacks critical behavioral details for a mutation tool.

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 extremely concise with a single sentence ('Set the backend for debugging'), which is front-loaded and wastes no words. Every part of the sentence contributes to the tool's purpose, making it efficient and well-structured for quick comprehension.

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 tool's complexity as a configuration mutation with no annotations and no output schema, the description is incomplete. It doesn't cover behavioral aspects like side effects, error conditions, or return values. For a tool that likely alters debugging state, more context is needed to ensure safe and correct usage by an AI agent.

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, with a clear enum for the 'backend' parameter. The description adds no additional meaning beyond what the schema provides, such as explaining the differences between backend options or default behaviors. Since the schema is comprehensive, the baseline score of 3 is appropriate, as the description doesn't enhance parameter understanding.

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 ('Set the backend for debugging'), which is clear but vague. It specifies the verb ('Set') and resource ('backend'), but doesn't distinguish it from sibling tools like 'configureLogging' or 'debug', nor does it explain what a 'backend' means in this context. 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 prerequisites, such as needing an active debugging session, or specify scenarios where setting the backend is necessary. With sibling tools like 'debug' and 'attach', there's no indication of how this tool fits into the workflow, leaving usage unclear.

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