Skip to main content
Glama

Get Server Information

get_server_info

Retrieve server details like version, storage path, and configuration to verify connection, debug issues, or troubleshoot problems with the Knowledge MCP Server.

Instructions

Shows server information including version from package.json.

When to use this tool:

  • Checking server version and capabilities

  • Debugging connection issues

  • Verifying server configuration

  • Getting storage path information

  • Troubleshooting problems

Key features:

  • Returns version information

  • Shows storage path configuration

  • Provides server description

  • Lightweight status check

You should:

  1. Use for initial connection verification

  2. Check when debugging issues

  3. Include in bug reports

  4. Verify server is responding

DO NOT use when:

  • Need git status (use get_storage_status)

  • Need to sync storage

  • Information already known

Returns: {success: bool, name: str, version: str, storage_path: str, description: str}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Asynchronous handler function implementing the core logic for 'get_server_info' tool, returning server configuration details including name, version, storage path, and description.
    getServerInfoAsync(): Promise<string> {
      const context = this.createContext('get_server_info', {});
    
      try {
        const result = {
          name: SERVER_CONFIG.name,
          version: SERVER_CONFIG.version,
          storage_path: STORAGE_PATH,
          description:
            'Knowledge MCP Server - Centralized project knowledge management via Model Context Protocol',
        };
    
        this.logSuccess('get_server_info', {}, context);
        return Promise.resolve(this.formatSuccessResponse(result));
      } catch (error) {
        this.logError(
          'get_server_info',
          {},
          error instanceof MCPError ? error : String(error),
          context
        );
        return Promise.resolve(this.formatErrorResponse(error, context));
      }
    }
  • Tool registration for 'get_server_info' using McpServer.registerTool, specifying title, description, empty input schema, and handler invocation.
    server.registerTool(
      'get_server_info',
      {
        title: 'Get Server Information',
        description: TOOL_DESCRIPTIONS.get_server_info,
        inputSchema: {},
      },
      async () => {
        const result = await serverHandler.getServerInfoAsync();
        return {
          content: [
            {
              type: 'text',
              text: result,
            },
          ],
        };
      }
    );
  • Detailed description string for the 'get_server_info' tool used in the tool schema registration, including usage guidelines and expected return format.
      get_server_info: `Shows server information including version from package.json.
    
    When to use this tool:
    - Checking server version and capabilities
    - Debugging connection issues
    - Verifying server configuration
    - Getting storage path information
    - Troubleshooting problems
    
    Key features:
    - Returns version information
    - Shows storage path configuration
    - Provides server description
    - Lightweight status check
    
    You should:
    1. Use for initial connection verification
    2. Check when debugging issues
    3. Include in bug reports
    4. Verify server is responding
    
    DO NOT use when:
    - Need git status (use get_storage_status)
    - Need to sync storage
    - Information already known
    
    Returns: {success: bool, name: str, version: str, storage_path: str, description: str}`,
Behavior4/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 effectively describes key features (e.g., returns version information, shows storage path configuration, provides server description, lightweight status check) and usage behaviors (e.g., use for initial connection verification, include in bug reports), though it could add more on error handling or performance. No contradictions with annotations exist.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is well-structured with sections like 'When to use this tool', 'Key features', 'You should', and 'DO NOT use when', but it is somewhat verbose with repetitive points (e.g., debugging mentioned multiple times). Some sentences could be condensed to improve efficiency without losing clarity.

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

Completeness4/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 largely complete, covering purpose, usage, and return values. However, it lacks details on error cases or specific server capabilities, which could enhance context for an AI agent in edge scenarios.

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 appropriately focuses on usage and output without redundant parameter details, earning a baseline score of 4 for handling this efficiently.

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 as showing server information including version from package.json, which is a specific verb+resource combination. However, it doesn't explicitly distinguish this from sibling tools like 'get_storage_status' beyond the 'DO NOT use when' section, which mentions it but doesn't fully articulate the functional difference.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides explicit guidance on when to use this tool (e.g., checking server version, debugging connection issues, initial connection verification) and when not to use it (e.g., when needing git status, to sync storage, or if information is already known), including a named alternative ('get_storage_status'). This covers both positive and negative scenarios comprehensively.

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

Related 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/sven-borkert/knowledge-mcp'

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