Skip to main content
Glama
martinchen448

SearXNG MCP Server

get_config

Retrieve SearXNG instance configuration to discover available search engines, enabled categories, supported languages, and instance settings for understanding search capabilities.

Instructions

Get the configuration of the SearXNG instance.

This tool retrieves the SearXNG instance configuration including available search engines, enabled categories, supported locales, plugins, and instance settings. Useful for understanding what capabilities are available.

Use this when you need to:

  • Discover available search engines

  • See what categories are enabled

  • Check supported languages/locales

  • Understand instance capabilities and settings

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The core handler function that executes the get_config tool logic by fetching the SearXNG configuration from the /config endpoint and returning it as JSON.
    async def get_config(self) -> Dict[str, Any]:
        """Get the configuration of the SearXNG instance.
    
        Returns:
            Dictionary containing instance configuration
    
        Raises:
            httpx.HTTPError: If the request fails
        """
        url = urljoin(self.base_url, "/config")
    
        response = await self.client.get(url)
        response.raise_for_status()
    
        return response.json()
  • Registration of the get_config tool in the MCP server's list_tools() function, including the tool name, description, and input schema (no required parameters).
                    Tool(
                        name="get_config",
                        description="""Get the configuration of the SearXNG instance.
                        
    This tool retrieves the SearXNG instance configuration including available search
    engines, enabled categories, supported locales, plugins, and instance settings.
    Useful for understanding what capabilities are available.
    
    Use this when you need to:
    - Discover available search engines
    - See what categories are enabled
    - Check supported languages/locales
    - Understand instance capabilities and settings""",
                        inputSchema={
                            "type": "object",
                            "properties": {},
                        },
                    ),
  • Input schema definition for the get_config tool, specifying an empty object (no input parameters required).
    inputSchema={
        "type": "object",
        "properties": {},
    },
  • Dispatch handler in the MCP server's call_tool() function that invokes the client.get_config() method and formats the response as TextContent for the MCP protocol.
    elif name == "get_config":
        config = await client.get_config()
        return [
            TextContent(
                type="text",
                text=json.dumps(config, indent=2),
            )
        ]
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 of behavioral disclosure. It clearly indicates this is a read-only operation ('retrieves') and specifies what data is returned, but lacks details on potential rate limits, authentication requirements, error conditions, or response format. The description adds useful context about the scope of configuration data but doesn't fully compensate for the absence of annotations.

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 well-structured and front-loaded with the core purpose in the first sentence. Each subsequent sentence and bullet point adds specific value without redundancy. The bullet points efficiently organize usage scenarios, making the description easy to scan while maintaining complete information.

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?

For a zero-parameter read-only tool with no output schema, the description provides comprehensive information about what configuration data is retrieved and when to use it. However, it doesn't describe the response format or structure, which would be helpful given the absence of an output schema. The description covers the essential context but leaves some ambiguity about what the return data looks like.

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 baseline is 4. The description appropriately doesn't discuss parameters since none exist, and instead focuses on explaining what configuration data will be retrieved, which adds value beyond the empty schema.

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 specific action ('retrieves') and resource ('SearXNG instance configuration'), listing concrete components like search engines, categories, locales, plugins, and settings. It distinguishes from siblings like 'search' (which performs searches) and 'get_suggestions' (which provides query suggestions) by focusing on configuration discovery rather than search operations.

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 explicitly provides four bullet points detailing when to use this tool: to discover available search engines, see enabled categories, check supported languages/locales, and understand instance capabilities. It implicitly distinguishes from 'search' (which is for executing searches) and 'get_suggestions' (for query autocompletion) by focusing on configuration discovery rather than search 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/martinchen448/searxng-mcp-server'

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