Skip to main content
Glama
Lspace-io

Lspace MCP Server

Official
by Lspace-io

lspace_get_repository_info

Retrieve detailed configuration and settings for a specific repository using the Lspace MCP Server, enabling accessible and searchable knowledge management across AI sessions.

Instructions

ℹ️ SETUP: Get detailed configuration for a specific repository.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
repositoryNameYesThe unique name of the repository.

Implementation Reference

  • Handler implementation for the 'lspace_get_repository_info' tool. Validates input, retrieves repository configs using RepositoryManager, finds the matching repo by name or ID, and returns formatted details about the repository including type, path, GitHub info if applicable, and knowledge base path.
    case 'lspace_get_repository_info':
      if (!args || !args.repositoryName) {
        return {
          jsonrpc: "2.0",
          id,
          error: {
            code: -32000,
            message: 'Missing required parameter: repositoryName'
          }
        };
      }
      
      if (!this.isInitialized || !this.repositoryManager) {
        return {
          jsonrpc: "2.0",
          id,
          error: {
            code: -32000,
            message: 'Repository manager not initialized'
          }
        };
      }
      
      try {
        const repoIdentifier = args.repositoryName;
        const repositories = this.repositoryManager.getAllRepositoryConfigs();
        
        // Find repository by name (case-insensitive) OR by ID
        const repo = repositories.find(r => 
          r.name.toLowerCase() === repoIdentifier.toLowerCase() ||
          r.id === repoIdentifier
        );
        
        if (!repo) {
          return {
            jsonrpc: "2.0",
            id,
            result: {
              content: [
                {
                  type: "text",
                  text: `Repository "${repoIdentifier}" not found.\n\nAvailable repositories:\n${repositories.map(r => `• ${r.name} (${r.id})`).join('\n')}`
                }
              ]
            }
          };
        }
        
        // Build detailed info
        let details = `Repository Details:\n• ID: ${repo.id}\n• Name: ${repo.name}\n• Type: ${repo.type}`;
        
        if (repo.type === 'local') {
          details += `\n• Path: ${repo.path}`;
        } else if (repo.type === 'github') {
          details += `\n• GitHub: ${repo.owner}/${repo.repo}\n• Branch: ${repo.branch}\n• PAT Alias: ${repo.pat_alias}`;
        }
        
        if (repo.path_to_kb) {
          details += `\n• Knowledge Base Path: ${repo.path_to_kb}`;
        }
        
        return {
          jsonrpc: "2.0",
          id,
          result: {
            content: [
              {
                type: "text",
                text: details
              }
            ]
          }
        };
      } catch (error) {
        return {
          jsonrpc: "2.0",
          id,
          error: {
            code: -32000,
            message: `Failed to get repository details: ${error.message}`
          }
        };
      }
  • Tool registration in getTools() method, including name, description, and input schema requiring 'repositoryName'.
    {
      name: "lspace_get_repository_info",
      description: "ℹ️ SETUP: Get detailed configuration for a specific repository.",
      inputSchema: {
        type: "object",
        properties: {
          repositoryName: {
            type: "string",
            description: "The unique name of the repository."
          }
        },
        required: ["repositoryName"]
      }
    },
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. It states this is a read operation ('Get'), which implies it's likely safe and non-destructive, but doesn't disclose behavioral traits such as authentication needs, rate limits, error handling, or what 'detailed configuration' entails in terms of output format. This leaves significant gaps for an agent to understand how to use it effectively.

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 zero waste. It uses an emoji for visual clarity and is front-loaded with the key action and resource. Every word earns its place, making it easy 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 (1 parameter, no output schema, no annotations), the description is adequate but incomplete. It covers the basic purpose but lacks details on behavioral aspects like what 'detailed configuration' includes or usage context. Without annotations or output schema, the description should do more to compensate, but it meets a minimum viable standard.

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 'repositoryName' clearly documented as 'The unique name of the repository.' The description adds no additional parameter semantics beyond what the schema provides, such as examples or constraints. With high schema coverage, the baseline score of 3 is appropriate, as the schema does the heavy lifting.

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 action ('Get detailed configuration') and target resource ('for a specific repository'), making the purpose understandable. It distinguishes from siblings like 'lspace_list_repositories' by focusing on a single repository's details rather than listing all repositories. However, it doesn't explicitly mention what 'detailed configuration' includes, leaving some ambiguity.

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 minimal guidance with 'SETUP' implying this might be used for initial configuration checks, but it doesn't specify when to use this tool versus alternatives like 'lspace_list_repositories' for overviews or other tools for content management. No explicit when-not-to-use or prerequisite information is given.

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/Lspace-io/lspace-server'

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