Skip to main content
Glama
jhstatewide

MCP Server SearXNG

by jhstatewide

web_search

Find relevant web content by submitting search queries with customizable parameters like language, time range, and safe search. Returns structured JSON results with configurable offset and result count for precise pagination.

Instructions

Performs a web search using SearXNG and returns structured JSON results.

IMPORTANT: Pagination is offset-based, NOT page-based.

To get a specific range of results, set 'offset' to the zero-based index of the first result you want, and 'max_results' to how many results you want. For example, to get results 40-43, set offset=39 and max_results=4.

Pagination: Use offset (not page) - offset=0=first result, offset=10=11th result

Example: offset=39, max_results=4 gets results 40-43

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesSearch terms. Example: 'climate change'
max_resultsNoNumber of results to return (1-100, default: 10)
offsetNoNumber of results to skip (default: 0)
content_lengthNoMax characters per result (0 for no content, only metadata; 1-1000, default: 200)
pageNo(Advanced) Page number. Usually leave as default.
languageNoLanguage code (e.g. 'en', 'all'). Default: 'all'all
time_rangeNoTime range: 'all_time', 'day', 'week', 'month', 'year'all_time
safesearchNoSafe search: 0 (off, default), 1 (moderate), 2 (strict)
Behavior3/5

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

With no annotations, the description covers pagination behavior adequately. However, it does not disclose other behavioral traits such as rate limits, authentication requirements, or data freshness.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is somewhat repetitive (the example is given twice) and longer than necessary. However, it is well-structured with clear sections and bolded warnings.

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 number of parameters and full schema coverage, the description is adequate. It explains pagination but lacks detail on the return value structure or error handling.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so parameters are well-documented. The description adds value by clarifying offset-based pagination with examples, but does not significantly enhance understanding beyond the 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 that it performs a web search using SearXNG and returns structured JSON results. It explicitly differentiates pagination as offset-based, avoiding confusion with page-based pagination.

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

Usage Guidelines4/5

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

The description provides clear usage guidelines with examples on how to use offset and max_results to retrieve specific result ranges. It does not mention alternative tools, but no siblings are provided.

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

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