Skip to main content
Glama
Lspace-io

Lspace MCP Server

Official
by Lspace-io

lspace_list_repositories

Retrieve and display all repositories managed by the Lspace MCP Server, enabling users to access and organize AI session insights efficiently.

Instructions

πŸ“‹ SETUP: List all repositories currently managed by Lspace.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Main execution logic for the lspace_list_repositories tool. Checks initialization, fetches repository configs from RepositoryManager, formats a list of repositories with their details, or returns appropriate messages/errors.
    case 'lspace_list_repositories':
      if (!this.isInitialized) {
        return {
          jsonrpc: "2.0",
          id,
          error: {
            code: -32000,
            message: 'Repository manager not initialized'
          }
        };
      }
      
      try {
        const repositories = this.repositoryManager.getAllRepositoryConfigs();
        
        if (repositories.length === 0) {
          return {
            jsonrpc: "2.0",
            id,
            result: {
              content: [
                {
                  type: "text",
                  text: "No repositories are currently managed by Lspace."
                }
              ]
            }
          };
        }
        
        return {
          jsonrpc: "2.0",
          id,
          result: {
            content: [
              {
                type: "text",
                text: `Found ${repositories.length} managed repositories:\n\n` +
                     repositories.map(repo => 
                       `β€’ ${repo.name} (${repo.id})\n  Type: ${repo.type}\n` +
                       (repo.type === 'local' ? `  Path: ${repo.path}\n` : '') +
                       (repo.type === 'github' ? `  GitHub: ${repo.owner}/${repo.repo} (${repo.branch})\n` : '') +
                       (repo.path_to_kb ? `  KB Path: ${repo.path_to_kb}\n` : '')
                     ).join('\n')
              }
            ]
          }
        };
      } catch (error) {
        return {
          jsonrpc: "2.0",
          id,
          error: {
            code: -32000,
            message: `Failed to list repositories: ${error.message}`
          }
        };
      }
  • Tool registration in getTools() method, defining name, description, and empty input schema (no parameters required).
    {
      name: "lspace_list_repositories",
      description: "πŸ“‹ SETUP: List all repositories currently managed by Lspace.",
      inputSchema: {
        type: "object",
        properties: {},
        required: []
      }
    },
  • Input schema definition for the tool (empty object, no required parameters).
      inputSchema: {
        type: "object",
        properties: {},
        required: []
      }
    },
Behavior2/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. While it indicates this is a listing operation, it doesn't describe important behavioral traits such as whether the list is paginated, sorted, or filtered; what format the output takes; or any rate limits or authentication requirements. The description is too minimal 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 extremely conciseβ€”a single sentence with an emoji prefix for visual clarity. It's front-loaded with the key action and resource, with no wasted words. Every element (the emoji, 'SETUP' context, and core description) serves a purpose in communicating the tool's function efficiently.

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 lack of annotations and output schema, the description is incomplete for effective use. It doesn't explain what the output looks like (e.g., a list of repository names, IDs, or metadata), any limitations (e.g., only active repositories), or behavioral aspects like error handling. For a tool with zero structured metadata, the description should provide more operational context.

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 zero parameters, and schema description coverage is 100%, so there are no parameters to document. The description appropriately doesn't discuss parameters, which is correct for a parameterless tool. It could potentially mention that no filtering or options are available, but this isn't strictly necessary.

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 ('List all repositories') and resource ('repositories currently managed by Lspace'), making the purpose immediately understandable. However, it doesn't explicitly differentiate this tool from its sibling 'lspace_get_repository_info', which might provide more detailed information about individual repositories rather than a comprehensive list.

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

Usage Guidelines3/5

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

The description implies usage context with 'πŸ“‹ SETUP:' and 'currently managed by Lspace', suggesting this is for inventory or setup purposes. However, it doesn't provide explicit guidance on when to use this tool versus alternatives like 'lspace_browse_knowledge_base' or 'lspace_search_knowledge_base', leaving some ambiguity about the best use cases.

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