NetLens
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| NETLENS_CACHE_TTL | No | Seconds to reuse a fetched page; 0 disables caching | 300 |
| NETLENS_MAX_BYTES | No | Cap on a single response; larger ones are truncated | 10485760 |
| NETLENS_HOST_DELAY | No | Minimum seconds between requests to the same host | 0.5 |
| NETLENS_USER_AGENT | No | Override the request User-Agent | Chrome UA |
| NETLENS_SEARXNG_URL | No | SearXNG base URL, e.g. http://192.168.1.10:8888 | |
| NETLENS_SEARCH_ENGINE | No | Default search backend | auto |
| NETLENS_REQUEST_TIMEOUT | No | Ceiling on a single tool call | 120 |
| NETLENS_SEARXNG_TIMEOUT | No | Seconds before an unreachable SearXNG is skipped | 8 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| web_searchA | Search the web and return real result links (title, URL, snippet), parsed locally from a search engine's HTML endpoint via a direct, bot-bypassing fetch. Returns LINKS, not summaries — follow up with web_fetch to read a result's full content. Returns the full first page of results (~10); a search fetches one page, so refine the query rather than expecting deep pagination. WORKFLOW: web_search to find pages, then web_fetch to read them. |
| web_fetchA | Fetch ANY web page directly and return its FULL content as clean Markdown (not a summary). Uses browser-like headers to get past common bot filters that block naive/robots-respecting clients (e.g. 403/202 to non-browser clients). Requests go straight to the target site; HTML is converted to Markdown locally (no third-party proxy/reader). Content is found by selecting the page's main content region and pruning navigation rails, so surrounding chrome is left out without ever risking the article. mode='article' (default) returns that region; mode='full' keeps the whole page body; mode='raw' returns unconverted HTML. Does NOT solve full JS/Cloudflare challenge pages or CAPTCHAs. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 2 tools
web_search and web_fetch have clearly distinct purposes: one finds relevant URLs via search, the other retrieves full page content. The descriptions explicitly differentiate them and explain their complementary workflow, eliminating any ambiguity.
Both tools follow the consistent verb_noun pattern (web_search, web_fetch), making the naming predictable and easy to understand.
Only 2 tools is minimal, but for a narrow focus on web searching and fetching, it's plausible. However, it feels slightly thin for a general-purpose server, as many use cases might require additional tools.
The tool surface covers only search and fetch, lacking tools for pagination, saving results, or handling multiple search engines. This leaves obvious gaps for a comprehensive web research workflow, potentially causing agent failures.