Skip to main content
Glama

get_configuration

Retrieve current configuration settings from the cmd-line-mcp server to access terminal command permissions and security controls.

Instructions

Get the current configuration settings.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function 'get_configuration' retrieves and formats the current system configuration settings, including server info, security details, and command statistics.
    async def get_configuration() -> Dict[str, Any]:
        """
        Get the current configuration settings.
    
        Returns:
            The current configuration settings
        """
        # Get a safe copy of the configuration
        config_copy = self.config.get_all()
    
        # Format it for display
        return {
            "server": config_copy["server"],
            "security": config_copy["security"],
            "commands": {
                "read_count": len(config_copy["commands"]["read"]),
                "write_count": len(config_copy["commands"]["write"]),
                "system_count": len(config_copy["commands"]["system"]),
                "blocked_count": len(config_copy["commands"]["blocked"]),
                "dangerous_patterns_count": len(
                    config_copy["commands"]["dangerous_patterns"]
                ),
                "full_command_lists": config_copy["commands"],
            },
            "output": config_copy["output"],
            "separator_support": self.config.has_separator_support(),
            "directory_whitelisting": {
                "enabled": True,
                "whitelisted_directories": self.whitelisted_directories,
                "note": "Directories not in this list will require session approval",
            },
        }
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, yet it fails to mention what format the configuration is returned in, whether it contains sensitive data, or any caching behavior.

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

Conciseness4/5

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

The single sentence is efficiently structured and front-loaded, containing no wasted words, though the overall description is under-specified rather than excessively verbose.

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 absence of an output schema and annotations, the description should indicate what configuration scope is returned (e.g., server settings, command paths, approved directories). As it stands, the agent cannot predict what data structure or content to expect.

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 accepts zero parameters, meeting the baseline score of 4 for this dimension as no additional parameter semantics are required beyond the empty schema.

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

Purpose3/5

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

The description states the basic action (Get) and resource (configuration settings), but does not specify what system or component's configuration is being retrieved, nor does it differentiate from sibling information-retrieval tools like get_command_help or list_available_commands.

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?

No guidance is provided on when to use this tool versus alternatives, or what prerequisites might exist for accessing configuration data.

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/wwqdrh/MCPcmd'

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