Skip to main content
Glama
DollhouseMCP

DollhouseMCP

Official

get_build_info

Retrieve comprehensive build and runtime details about the MCP server to understand its current configuration and operational status.

Instructions

Get comprehensive build and runtime information about the server

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The MCP tool handler for 'get_build_info' which calls the BuildInfoService to get and format the information, returning it as text content.
      handler: async () => {
        const info = await buildInfoService.getBuildInfo();
        const formattedInfo = buildInfoService.formatBuildInfo(info);
        return {
          content: [
            {
              type: "text",
              text: formattedInfo
            }
          ]
        };
      }
    }
  • Exports the tool registration array for 'get_build_info' including name, description, empty input schema, and handler reference.
    export function getBuildInfoTools(_server: IToolHandler) {
      const buildInfoService = BuildInfoService.getInstance();
    
      return [
        {
          tool: {
            name: 'get_build_info',
            description: 'Get comprehensive build and runtime information about the server',
            inputSchema: {
              type: 'object' as const,
              properties: {},
              required: []
            }
          },
          handler: async () => {
            const info = await buildInfoService.getBuildInfo();
            const formattedInfo = buildInfoService.formatBuildInfo(info);
            return {
              content: [
                {
                  type: "text",
                  text: formattedInfo
                }
              ]
            };
          }
        }
      ];
    }
  • Core helper method that gathers package, build (git/package timestamp), runtime, environment, and server information.
    public async getBuildInfo(): Promise<BuildInfo> {
      const [packageInfo, gitInfo, dockerInfo] = await Promise.all([
        this.getPackageInfo(),
        this.getGitInfo(),
        this.getDockerInfo()
      ]);
    
      const buildTimestamp = await this.getBuildTimestamp();
    
      return {
        package: packageInfo,
        build: {
          timestamp: buildTimestamp,
          type: gitInfo.commit ? 'git' : buildTimestamp ? 'npm' : 'unknown',
          gitCommit: gitInfo.commit,
          gitBranch: gitInfo.branch,
          collectionFix: 'v1.6.9-beta1-collection-fix'  // Version identifier for verification
        },
        runtime: {
          nodeVersion: process.version,
          platform: process.platform,
          arch: process.arch,
          uptime: process.uptime(),
          memoryUsage: process.memoryUsage()
        },
        environment: {
          nodeEnv: process.env.NODE_ENV,
          isProduction: process.env.NODE_ENV === 'production',
          isDevelopment: process.env.NODE_ENV === 'development',
          isDebug: process.env.DEBUG === 'true' || process.env.DEBUG === '1',
          isDocker: dockerInfo.isDocker,
          dockerInfo: dockerInfo.info
        },
        server: {
          startTime: this.startTime,
          uptime: Date.now() - this.startTime.getTime(),
          mcpConnection: true // We're connected if this method is being called via MCP
        }
      };
    }
  • TypeScript interface defining the structure of build information returned by getBuildInfo.
    export interface BuildInfo {
      package: {
        name: string;
        version: string;
      };
      build: {
        timestamp?: string;
        type: 'git' | 'npm' | 'unknown';
        gitCommit?: string;
        gitBranch?: string;
        collectionFix?: string;  // Version identifier for verification
      };
      runtime: {
        nodeVersion: string;
        platform: string;
        arch: string;
        uptime: number;
        memoryUsage: NodeJS.MemoryUsage;
      };
      environment: {
        nodeEnv?: string;
        isProduction: boolean;
        isDevelopment: boolean;
        isDebug: boolean;
        isDocker: boolean;
        dockerInfo?: string;
      };
      server: {
        startTime: Date;
        uptime: number;
        mcpConnection: boolean;
      };
    }
  • Registers the get_build_info tool (and others from getBuildInfoTools) into the main tool registry during server setup.
    // Register build info tools
    this.toolRegistry.registerMany(getBuildInfoTools(instance));
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. While 'Get' implies a read-only operation, it doesn't specify whether this requires authentication, has rate limits, returns structured data, or impacts server performance. For a tool with zero annotation coverage, this leaves significant gaps in understanding its behavior.

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 without any wasted words. It directly communicates what the tool does in a clear and structured manner, making it easy for an agent to parse quickly.

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 low complexity (0 parameters, no output schema), the description is minimally adequate. However, with no annotations and many sibling tools, it lacks context about what 'build and runtime information' entails or how it differs from other status-related tools. This makes it incomplete for optimal agent decision-making in a crowded toolset.

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 tool has 0 parameters, and the input schema has 100% description coverage, so there are no parameters to document. The description doesn't need to add parameter semantics, but it could have mentioned the lack of inputs. A baseline of 4 is appropriate since no parameter information is required.

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 tool's purpose with a specific verb ('Get') and resource ('comprehensive build and runtime information about the server'), making it immediately understandable. However, it doesn't explicitly differentiate itself from sibling tools like 'portfolio_status' or 'oauth_helper_status' that might also provide status information, which prevents a perfect 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 many sibling tools related to status, configuration, and management, there's no indication of whether this is for diagnostics, monitoring, or general information, leaving the agent to guess based on the name alone.

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/DollhouseMCP/mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server