Skip to main content
Glama

list_config_sources

View all registered configuration sources from git repositories. Identify available sources for fetching configurations.

Instructions

List all registered config sources. Shows git repositories that have been registered with add_config_source. Use this to see available sources for fetch_config.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
enabled_onlyNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • Primary handler function for list_config_sources tool. Takes args dict with optional 'enabled_only' parameter. Uses SourceManager.list_sources() to fetch source list and formats the output as a TextContent result.
    async def list_config_sources_tool(args: dict) -> list[TextContent]:
        """
        List all registered config sources.
    
        Shows git repositories that have been registered with add_config_source.
    
        Args:
            args: Dictionary containing:
                - enabled_only: Only show enabled sources (default: false)
    
        Returns:
            List of TextContent with source list
        """
        from skill_seekers.mcp.source_manager import SourceManager
    
        enabled_only = args.get("enabled_only", False)
    
        try:
            source_manager = SourceManager()
            sources = source_manager.list_sources(enabled_only=enabled_only)
    
            if not sources:
                result = """📋 No config sources registered
    
    To add a source:
      add_config_source(
        name="team",
        git_url="https://github.com/myorg/configs.git"
      )
    
    💡 Once added, use: fetch_config(source="team", config_name="...")
    """
                return [TextContent(type="text", text=result)]
    
            # Format sources list
            result = f"📋 Config Sources ({len(sources)} total"
            if enabled_only:
                result += ", enabled only"
            result += ")\n\n"
    
            for source in sources:
                status_icon = "✓" if source.get("enabled", True) else "✗"
                result += f"{status_icon} **{source['name']}**\n"
                result += f"  📁 {source['git_url']}\n"
                result += f"  🔖 Type: {source['type']} | 🌿 Branch: {source['branch']}\n"
                result += f"  🔑 Token: {source.get('token_env', 'None')} | ⚡ Priority: {source['priority']}\n"
                result += f"  🕒 Added: {source['added_at'][:19]}\n"
                result += "\n"
    
            result += """Usage:
      # Fetch config from a source
      fetch_config(source="SOURCE_NAME", config_name="CONFIG_NAME")
    
      # Add new source
      add_config_source(name="...", git_url="...")
    
      # Remove source
      remove_config_source(name="SOURCE_NAME")
    """
    
            return [TextContent(type="text", text=result)]
    
        except Exception as e:
            return [TextContent(type="text", text=f"❌ Error: {str(e)}")]
  • FastMCP-decorated tool registration for list_config_sources. Defines the MCP tool with description 'List all registered config sources' and parameter 'enabled_only' (bool, default false). Delegates to list_config_sources_impl.
    @safe_tool_decorator(
        description="List all registered config sources. Shows git repositories that have been registered with add_config_source. Use this to see available sources for fetch_config."
    )
    async def list_config_sources(enabled_only: bool = False) -> str:
        """
        List all registered config sources.
    
        Args:
            enabled_only: Only show enabled sources (default: false)
    
        Returns:
            List of registered sources with details.
        """
        result = await list_config_sources_impl({"enabled_only": enabled_only})
        if isinstance(result, list) and result:
            return result[0].text if hasattr(result[0], "text") else str(result[0])
        return str(result)
  • The args schema accepted by list_config_sources_tool: accepts a dictionary with optional 'enabled_only' key (bool, default false).
    async def list_config_sources_tool(args: dict) -> list[TextContent]:
        """
        List all registered config sources.
    
        Shows git repositories that have been registered with add_config_source.
    
        Args:
            args: Dictionary containing:
                - enabled_only: Only show enabled sources (default: false)
    
        Returns:
            List of TextContent with source list
        """
  • Re-exports list_config_sources_tool as list_config_sources_impl for use by server_fastmcp.py.
    from .source_tools import (
        list_config_sources_tool as list_config_sources_impl,
    )
  • SourceManager.list_sources() - The underlying data source. Reads the ~/.skill-seekers/sources.json registry and optionally filters by enabled status.
    def list_sources(self, enabled_only: bool = False) -> list[dict]:
        """
        List all config sources.
    
        Args:
            enabled_only: If True, only return enabled sources
    
        Returns:
            List of source dictionaries (sorted by priority)
        """
        registry = self._read_registry()
    
        if enabled_only:
            return [s for s in registry["sources"] if s.get("enabled", True)]
    
        return registry["sources"]
Behavior3/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. It correctly describes the listing behavior (read-only) but does not disclose any additional traits like pagination, permissions, or response format. For a simple list operation, this is adequate but not exceptional.

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, consisting of two sentences that convey purpose and usage advice without any unnecessary words or repetition.

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 simplicity of the tool (single optional boolean parameter, output schema present), the description covers the main purpose and usage context. It relates to sibling tools. The only minor gap is the lack of parameter explanation, but overall it is sufficiently complete for a list operation.

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

Parameters2/5

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

Schema description coverage is 0%, meaning the description must compensate. However, the description does not mention the 'enabled_only' parameter at all. The parameter name suggests a filter, but the agent gets no detailed guidance, leaving a gap in understanding.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb and resource: 'List all registered config sources' and specifies 'git repositories that have been registered with add_config_source.' It distinguishes from siblings like add_config_source and fetch_config.

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

Usage Guidelines4/5

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

The description advises 'Use this to see available sources for fetch_config,' providing clear usage context. It does not explicitly state when not to use, but the advice is sufficient for typical scenarios.

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/yusufkaraaslan/Skill_Seekers'

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