Skip to main content
Glama
yawlhead91

MariaDB MCP Server

by yawlhead91

reload_config

Reload MariaDB server configuration from environment variables and .env files to apply changes without restarting the server.

Instructions

Reload configuration from environment variables and .env file.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The main handler function for the 'reload_config' tool. It closes the existing database connection, reloads the configuration from environment variables, updates the connection parameters, and resets the connection pool for the next operation.
    async def reload_config() -> str:
        """Reload configuration from environment variables and .env file."""
        try:
            # Close existing connection pool
            await db_connection.close()
            
            # Reload configuration
            config_manager.reload()
            
            # Update connection parameters
            db_connection.host = config_manager.get('host')
            db_connection.port = config_manager.get('port')
            db_connection.user = config_manager.get('user')
            db_connection.password = config_manager.get('password')
            db_connection.database = config_manager.get('database')
            db_connection.pool = None  # Reset pool to force reconnection
            
            logger.info("Configuration reloaded successfully")
            return "Configuration reloaded successfully. New connection will be established on next database operation."
            
        except Exception as e:
            logger.error(f"Error reloading configuration: {e}")
            return f"Error reloading configuration: {str(e)}"
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries the full burden. It states the action ('Reload') but doesn't disclose behavioral traits like whether it's safe, idempotent, requires permissions, or what happens on failure. It only mentions the sources, leaving key operational details unclear.

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 no wasted words. It's front-loaded with the core action and specifies sources clearly, making it highly concise and well-structured.

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 no parameters, annotations, or output schema (context signals indicate has_output_schema: true, but it's not provided here), the description is minimally adequate. It explains what the tool does but lacks details on behavior, output, or integration context, leaving 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?

There are 0 parameters, and schema description coverage is 100%, so no parameter information is needed. The description doesn't add param semantics, but with no params, a baseline of 4 is appropriate as it doesn't need to compensate for gaps.

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 ('Reload') and the resource ('configuration'), specifying the sources ('from environment variables and .env file'). It's specific but doesn't differentiate from siblings since no sibling tools handle configuration reloading, making a 5 inappropriate.

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 in what context it should be invoked. The description implies it's for reloading config, but lacks explicit usage scenarios or prerequisites.

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/yawlhead91/mariadb-mcp'

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