Skip to main content
Glama

version

Retrieve version details for the Delve debugger to verify installation and compatibility when debugging Go programs.

Instructions

Get Delve version information

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler logic for the 'version' tool: executes 'dlv version' command and returns its stdout as text content.
    case "version": {
      const { stdout } = await exec("dlv version");
      return {
        content: [{
          type: "text",
          text: stdout
        }]
      };
    }
  • Input schema definition for the 'version' tool (empty object, no parameters required).
      name: "version",
      description: "Get Delve version information",
      inputSchema: {
        type: "object",
        properties: {}
      }
    },
  • src/server.ts:415-418 (registration)
    Dispatches calls to the 'version' tool (and other config tools) to the handleConfigCommands function.
    // Configuration commands
    if (["setBackend", "configureLogging", "version"].includes(name)) {
      return handleConfigCommands(name, args);
    }
  • src/server.ts:351-357 (registration)
    Registers the 'version' tool in the ListTools response, including name, description, and schema.
      name: "version",
      description: "Get Delve version information",
      inputSchema: {
        type: "object",
        properties: {}
      }
    },
Behavior2/5

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

No annotations are provided, so the description carries full burden. 'Get' implies a read operation, but it doesn't disclose behavioral traits like whether it requires authentication, has rate limits, or what format the version information returns. This is inadequate for a 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 sentence that front-loads the core purpose with zero waste. Every word earns its place, making it highly concise and well-structured for quick understanding.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's simplicity (0 parameters, no output schema, no annotations), the description is minimally adequate. It states what the tool does but lacks context about return values or usage scenarios, leaving gaps in completeness for even a basic tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has 0 parameters with 100% coverage, so no parameter documentation is needed. The description doesn't add parameter details, which is appropriate, earning a baseline score of 4 for tools with no parameters.

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 'Get Delve version information' clearly states the verb ('Get') and resource ('Delve version information'), making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'core' or 'debug', which might also provide system information, so it doesn't reach the highest score.

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 sibling tools like 'core' and 'debug' that might offer related system information, there's no indication of context or prerequisites for choosing 'version' over other options.

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