Skip to main content
Glama
n24q02m

WET - Web Extended Toolkit

search

Read-onlyIdempotent

Search the web, academic repositories, and library documentation with filters for domains, time range, and enriched snippets.

Instructions

Find information across web, academic sources, or library docs. Returns search result listings (titles, URLs, snippets) -- NOT full page content. To read full content from a URL, use the extract tool instead.

Actions:

  • search: Web search via SearXNG. Example: search(action="search", query="python async patterns")

  • research: Academic/scientific search (Google Scholar, arXiv, PubMed). Example: search(action="research", query="transformer attention mechanism")

  • docs: Search library documentation with auto-indexing. Example: search(action="docs", query="how to create routes", library="fastapi")

  • docs_resolve: Free-form library name to ranked library_id list. Example: search(action="docs_resolve", query="react")

  • docs_query: Version-aware library docs query honoring project lock + token cap. Example: search(action="docs_query", library="react", version="latest", topic="useState", query="how to set initial state")

  • docs_lock_project: Detect project manifests (pyproject/package.json/go.mod/Cargo.toml) and lock the library set for Cabinets isolation. Example: search(action="docs_lock_project", project_path="/repo/my-app")

  • similar: Find pages similar to a URL (pass URL as query). Example: search(action="similar", query="https://example.com/article")

Key parameters:

  • query (required for all actions): Search terms or URL (for similar)

  • library (required for docs): Library name, e.g. "react", "fastapi"

  • language: Programming language for disambiguation in docs, e.g. "python", "java"

  • expand: Enable LLM query expansion for broader coverage (default: false)

  • enrich: Fetch actual page content for richer snippets (default: false, adds latency)

  • max_results: Number of results (default: 10)

  • time_range: Recency filter -- day, week, month, year

  • include_domains / exclude_domains: Domain filters

Use help tool with tool_name="search" for full parameter documentation.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actionYes
queryNo
libraryNo
versionNo
topicNo
project_pathNo
languageNo
categoriesNogeneral
max_resultsNo
limitNo
time_rangeNo
include_domainsNo
exclude_domainsNo
expandNo
enrichNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

Annotations indicate readOnlyHint=true, idempotentHint=true, openWorldHint=true. The description adds valuable context: returns listings only (not full content), notes expansion and enrichment behaviors, and mentions auto-indexing for docs. No contradiction.

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 with sections for each action and key parameters, but it is somewhat lengthy. It is front-loaded with main purpose and alternative, making it efficient overall.

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 15 parameters, 1 required, and multiple sub-actions, the description covers usage patterns, parameter explanations, and examples thoroughly. Output schema exists, so return values need not be detailed.

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

Parameters5/5

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

Schema has 0% description coverage, so the description compensates fully. It explains the 'action' parameter with all variants, and key parameters like query, library, language, expand, enrich, max_results, time_range, and domain filters with examples.

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: finding information across web, academic sources, or library docs. It distinguishes from sibling tools like 'extract' (for full page content) and lists specific actions with examples.

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 explicitly notes when to use the 'extract' tool instead for full content. It provides action-specific examples but does not exhaustively cover when not to use each sub-action.

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/n24q02m/wet-mcp'

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