Skip to main content
Glama
martinchen448

SearXNG MCP Server

health_check

Verify the SearXNG instance is running and accessible to diagnose connection issues and ensure the search service is operational before performing searches.

Instructions

Check the health status of the SearXNG instance.

This tool verifies that the SearXNG instance is running and accessible. Useful for diagnostics and ensuring the search service is operational before performing searches.

Use this when you need to:

  • Verify the SearXNG instance is accessible

  • Diagnose connection issues

  • Check service availability before searching

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The health_check method in SearXNGClient class that executes the core logic: GET request to SearXNG /healthz endpoint and returns appropriate status dictionary.
    async def health_check(self) -> Dict[str, Any]:
        """Check the health status of the SearXNG instance.
    
        Returns:
            Dictionary containing health status information
    
        Raises:
            httpx.HTTPError: If the request fails
        """
        url = urljoin(self.base_url, "/healthz")
    
        try:
            response = await self.client.get(url)
            response.raise_for_status()
            return {"status": "ok", "message": "SearXNG instance is healthy"}
        except httpx.HTTPError as e:
            return {
                "status": "error",
                "message": f"Health check failed: {str(e)}",
            }
  • Registration of the 'health_check' tool in the MCP server's tool list, including name, description, and empty input schema (no parameters required).
                    Tool(
                        name="health_check",
                        description="""Check the health status of the SearXNG instance.
                        
    This tool verifies that the SearXNG instance is running and accessible. Useful for
    diagnostics and ensuring the search service is operational before performing searches.
    
    Use this when you need to:
    - Verify the SearXNG instance is accessible
    - Diagnose connection issues
    - Check service availability before searching""",
                        inputSchema={
                            "type": "object",
                            "properties": {},
                        },
                    ),
  • Input schema for health_check tool: empty object since the tool takes no parameters.
    inputSchema={
        "type": "object",
        "properties": {},
    },
Behavior3/5

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

With no annotations provided, the description carries the full burden. It discloses that the tool checks health status and accessibility, implying a read-only, non-destructive operation useful for diagnostics. However, it lacks details on error handling, response format, or potential side effects like network timeouts, leaving some behavioral aspects unclear.

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 well-structured and front-loaded with the core purpose, followed by usage guidelines in a bulleted list. It avoids unnecessary details, but the bulleted list could be slightly more concise (e.g., by combining related points), though overall it's efficient and easy to scan.

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 tool's simplicity (0 parameters, no output schema, no annotations), the description is reasonably complete. It explains the purpose, usage, and context effectively. However, without an output schema, it could benefit from briefly mentioning what the health check returns (e.g., status codes or messages), slightly limiting completeness for diagnostics.

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 the schema fully documents the input. The description appropriately adds no parameter-specific information, as none are needed, maintaining clarity without redundancy. This meets the baseline for tools with no parameters.

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 tool's purpose with specific verbs ('check', 'verifies') and resource ('SearXNG instance'), explicitly distinguishing it from sibling tools like 'search' by focusing on health verification rather than search operations. It directly answers what the tool does without being tautological.

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

Usage Guidelines5/5

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

The description provides explicit usage scenarios in a bulleted list (e.g., 'Verify the SearXNG instance is accessible', 'Diagnose connection issues'), clearly indicating when to use this tool. It implicitly distinguishes from alternatives like 'search' by specifying it's for pre-search availability checks, though it doesn't explicitly name sibling tools.

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/martinchen448/searxng-mcp-server'

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