Skip to main content
Glama

get_settings_info

Retrieve project configuration details to understand code repository settings and analysis parameters.

Instructions

Get information about the project settings.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • Core implementation of get_settings_info tool logic in SettingsService, handling settings retrieval, config/stats loading, and response formatting.
    def get_settings_info(self) -> Dict[str, Any]:
        """
        Get comprehensive settings information.
    
        Handles the logic for get_settings_info MCP tool.
    
        Returns:
            Dictionary with settings directory, config, stats, and status information
        """
        temp_dir = os.path.join(tempfile.gettempdir(), SETTINGS_DIR)
        
        # Get the actual index directory from the index manager
        index_manager = get_index_manager()
        actual_temp_dir = index_manager.temp_dir if index_manager.temp_dir else temp_dir
    
        # Check if base_path is set
        if not self.base_path:
            return ResponseFormatter.settings_info_response(
                settings_directory="",
                temp_directory=actual_temp_dir,
                temp_directory_exists=os.path.exists(actual_temp_dir),
                config={},
                stats={},
                exists=False,
                status="not_configured",
                message="Project path not set. Please use set_project_path to set a "
                        "project directory first."
            )
    
        # Get config and stats
        config = self.settings.load_config() if self.settings else {}
        stats = self.settings.get_stats() if self.settings else {}
        settings_directory = actual_temp_dir
        exists = os.path.exists(settings_directory) if settings_directory else False
    
        return ResponseFormatter.settings_info_response(
            settings_directory=settings_directory,
            temp_directory=actual_temp_dir,
            temp_directory_exists=os.path.exists(actual_temp_dir),
            config=config,
            stats=stats,
            exists=exists
        )
  • MCP tool registration using @mcp.tool() decorator with error handling wrapper that delegates to SettingsService.get_settings_info().
    @mcp.tool()
    @handle_mcp_tool_errors(return_type='dict')
    def get_settings_info(ctx: Context) -> Dict[str, Any]:
        """Get information about the project settings."""
        return SettingsService(ctx).get_settings_info()
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 'Get information' which implies a read-only operation, but lacks details on permissions, rate limits, response format, or error conditions. This is insufficient 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 a single, clear sentence with no wasted words. It is front-loaded with the core purpose, making it efficient and easy to parse, which is ideal for conciseness.

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 has 0 parameters, 100% schema coverage, and an output schema exists, the description's job is reduced. However, as a read operation with no annotations, it should ideally mention what kind of information is returned or typical use cases, leaving some gaps in completeness.

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 with 100% schema description coverage, so no parameter documentation is needed. The description does not add parameter details, but this is acceptable given the absence of parameters, warranting a baseline score above minimum viable.

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 verb ('Get') and resource ('information about the project settings'), making the purpose immediately understandable. However, it does not differentiate from potential sibling tools like 'clear_settings' or 'configure_file_watcher', 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 siblings like 'clear_settings' (for deletion) and 'configure_file_watcher' (for configuration), there is no explicit or implied context for choosing this read-only information retrieval tool.

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/johnhuang316/code-index-mcp'

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