Skip to main content
Glama
whw23

searxng-http-mcp

by whw23
OverviewSchemaRelated ServersScoreDiscussions
Python
Hybrid

search

Read-onlyIdempotent

Search the web using SearXNG, aggregating results from over 200 engines with privacy. Use categories to focus on specific content types or specify engines for precise sources.

Instructions

Search the web using SearXNG metasearch engine.

Aggregates results from 200+ search engines (Google, Bing, DuckDuckGo, Brave, etc.) with privacy. Returns results, answers, suggestions, corrections, and infoboxes. Use 'categories' to focus on specific content types. Use 'pages' for more results.

Not suitable for autocomplete suggestions (use autocomplete tool) or discovering available engines/categories (use engine_info tool). Results are cached for 60 seconds.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesThe search query to use
categoriesNoComma-separated category names to focus on (e.g., 'general,news,science'). Prefer this over 'engines' to narrow results — categories leverage multiple engines automatically. Call engine_info to discover available categories.
enginesNoComma-separated engine names to use (e.g., 'google,arxiv,wikipedia'). Only use when you need a specific source; otherwise prefer 'categories'. Overrides category-based engine selection when set.
languageNoSearch language code (e.g., 'en', 'zh', 'ja', 'de'). Filters results to the specified language. Omit to search all languages.
time_rangeNoRestrict results to those published within this time window. Omit for no time restriction.
safesearchNoSafe search level: 0=off, 1=moderate, 2=strict
pagenoNoStarting page number. Use with 'pages' for pagination.
pagesNoNumber of pages to fetch in parallel (multi-page fanout). Higher values return more results but increase latency. Use 2-3 for comprehensive research.
max_resultsNoMaximum number of results to return. Applied after aggregation across pages.
formatNoResult detail level: 'compact' returns title/url/content only, 'full' includes engines/score/category/date/thumbnailscompact

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Tool Definition Quality

A4.9/5.0
Behavior5/5

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

Annotations already declare readOnly, idempotent, openWorld. Description adds non-obvious behaviors: 'Aggregates results from 200+ search engines... with privacy', 'Returns results, answers, suggestions, corrections, and infoboxes', and 'Results are cached for 60 seconds'. No contradictions.

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?

Four sentences, each serving a distinct purpose: purpose statement, aggregation details, usage tips, exclusions, and caching behavior. No wasted words, front-loaded with core action.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given presence of output schema and detailed parameter descriptions, the description covers what is needed: it specifies return types (results, answers, etc.), clarifies caching, and references sibling tools. No gaps.

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?

Schema coverage is 100% (baseline 3). Description adds contextual usage guidance for 'categories' and 'pages' beyond schema descriptions. However, it does not elaborate on other parameters, but the schema itself is detailed.

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 'Search the web using SearXNG metasearch engine' (specific verb+resource) and distinguishes from siblings by specifying 'Not suitable for autocomplete suggestions (use autocomplete tool) or discovering available engines/categories (use engine_info tool)'.

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?

Explicitly tells when to use: 'Use categories to focus on specific content types. Use pages for more results.' and when not: 'Not suitable for autocomplete suggestions... or discovering available engines/categories'. Provides alternatives (autocomplete, engine_info).

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/whw23/searxng_http_mcp'

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