Skip to main content
Glama

get_server_configuration_status

Check Couchbase server status and verify configuration without establishing a connection to monitor operational health.

Instructions

Get the server status and configuration without establishing connection. This tool can be used to verify if the server is running and check the configuration.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function implementing the core logic of the 'get_server_configuration_status' tool. It retrieves and returns anonymized server configuration and connection status.
    def get_server_configuration_status(ctx: Context) -> dict[str, Any]:
        """Get the server status and configuration without establishing connection.
        This tool can be used to verify if the server is running and check the configuration.
        """
        settings = get_settings()
    
        # Don't expose sensitive information like passwords
        configuration = {
            "connection_string": settings.get("connection_string", "Not set"),
            "username": settings.get("username", "Not set"),
            "read_only_query_mode": settings.get("read_only_query_mode", True),
            "password_configured": bool(settings.get("password")),
            "ca_cert_path_configured": bool(settings.get("ca_cert_path")),
            "client_cert_path_configured": bool(settings.get("client_cert_path")),
            "client_key_path_configured": bool(settings.get("client_key_path")),
        }
    
        app_context = ctx.request_context.lifespan_context
        connection_status = {
            "cluster_connected": app_context.cluster is not None,
        }
    
        return {
            "server_name": MCP_SERVER_NAME,
            "status": "running",
            "configuration": configuration,
            "connections": connection_status,
        }
  • Import of the tool handler from server.py into the tools.__init__.py for inclusion in the ALL_TOOLS list used for MCP registration.
    from .server import (
        get_buckets_in_cluster,
        get_cluster_health_and_services,
        get_collections_in_scope,
        get_scopes_and_collections_in_bucket,
        get_scopes_in_bucket,
        get_server_configuration_status,
        test_cluster_connection,
    )
  • Loop that registers all tools from ALL_TOOLS, including 'get_server_configuration_status', to the FastMCP server instance.
    # Register all tools
    for tool in ALL_TOOLS:
        mcp.add_tool(tool)
  • The ALL_TOOLS list that includes the get_server_configuration_status tool for bulk registration in mcp_server.py.
    ALL_TOOLS = [
        get_buckets_in_cluster,
        get_server_configuration_status,
        test_cluster_connection,
        get_scopes_and_collections_in_bucket,
        get_collections_in_scope,
        get_scopes_in_bucket,
        get_document_by_id,
        upsert_document_by_id,
        delete_document_by_id,
        get_schema_for_collection,
        run_sql_plus_plus_query,
        get_index_advisor_recommendations,
        list_indexes,
        get_cluster_health_and_services,
        get_queries_not_selective,
        get_queries_not_using_covering_index,
        get_queries_using_primary_index,
        get_queries_with_large_result_count,
        get_queries_with_largest_response_sizes,
        get_longest_running_queries,
        get_most_frequent_queries,
    ]
  • Import of the ALL_TOOLS list containing the tool for registration.
    from tools import ALL_TOOLS
Behavior2/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 of behavioral disclosure. It mentions the tool can 'verify if the server is running and check the configuration', but doesn't specify what data is returned, potential limitations (e.g., read-only, no side effects), or error conditions. This leaves gaps in understanding the tool's 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 description is concise with two sentences that efficiently convey the tool's purpose and usage. It's front-loaded with the main action and avoids unnecessary details, though it could be slightly more structured by explicitly separating purpose from guidelines.

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 that the tool has no parameters, an output schema exists, and annotations are absent, the description is moderately complete. It covers the basic purpose but lacks details on return values (though the output schema helps) and behavioral traits like safety or performance, leaving room for improvement.

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, and the schema description coverage is 100%, so there's no need for parameter details in the description. The description appropriately focuses on the tool's purpose without redundant parameter information, earning a high baseline score.

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 tool's purpose with specific verbs ('get', 'verify', 'check') and resources ('server status and configuration'), making it easy to understand what it does. However, it doesn't explicitly differentiate from siblings like 'test_cluster_connection' or 'get_cluster_health_and_services', 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 Guidelines3/5

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

The description provides some implied usage context by stating 'without establishing connection', suggesting this is for non-invasive checks. However, it lacks explicit guidance on when to use this tool versus alternatives like 'test_cluster_connection' or 'get_cluster_health_and_services', which offer related functionality.

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/Couchbase-Ecosystem/mcp-server-couchbase'

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