Skip to main content
Glama
wtznicy

MyWebSearch

by wtznicy
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

search

Read-onlyIdempotent

Retrieve web results across multiple engines with no API key, with automatic routing for Chinese or English queries and concurrent multi-query support.

Instructions

Search the web across multiple engines with no API key required. searchMode: omit/auto = server SEARCH_MODE; request/playwright force that mode. Engine guidance: for Chinese queries prefer engines=["baidu","sogou","csdn","juejin"] (domestic engines have far better Chinese content coverage); for English/official docs use bing; overseas engines (duckduckgo/brave/startpage/exa) need a proxy. Omit engines to use server-side auto routing. Cite the relevant result URLs as markdown links in your answer. For OFFICIAL library/framework documentation, prefer resolveLibraryId + queryDocs (more reliable, works without proxy). Use the site: operator for site-specific queries (e.g. "update site:docs.elastic.co").

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMax results (default: server DEFAULT_SEARCH_LIMIT, usually 10)
queryNoSingle search query (use queries for multi-intent fan-out)
enginesNoSearch engines to use (default: server default, which may auto-route by query language)
queriesNo1-4 queries run concurrently and merged (dedup by URL) — for covering multiple intents in one call (e.g. official docs / Chinese community / English)
minResultsNoAuto-run additional engines when fewer than this many USABLE results (relevant, non-entry-page) come back (default: server DEFAULT_MIN_RESULTS, usually 5)
searchModeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changedv1.0.15
    • removedInput schema / properties / engines / default
      Removed value: -[
-  "bing"
-]
    • addedInput schema / properties / engines / description
      Added value: +"Search engines to use (default: server default, which may auto-route by query language)"
    • removedInput schema / properties / limit / default
      Removed value: -10
    • addedInput schema / properties / limit / description
      Added value: +"Max results (default: server DEFAULT_SEARCH_LIMIT, usually 10)"
    • changedInput schema / properties / minResults / description
      Previous value: -"Auto-run additional engines when fewer than this many results come back (default: disabled)"New value: +"Auto-run additional engines when fewer than this many USABLE results (relevant, non-entry-page) come back (default: server DEFAULT_MIN_RESULTS, usually 5)"
    • addedInput schema / properties / queries
      Added value: +{
+  "description": "1-4 queries run concurrently and merged (dedup by URL) — for covering multiple intents in one call (e.g. official docs / Chinese community / English)",
+  "items": {
+    "maxLength": 500,
+    "minLength": 1,
+    "type": "string"
+  },
+  "maxItems": 4,
+  "minItems": 1,
+  "type": "array"
+}
    • addedInput schema / properties / query / description
      Added value: +"Single search query (use queries for multi-intent fan-out)"
    • removedInput schema / required
      Removed value: -[
-  "query"
-]
  2. First observedv1.0.11

TDQS

A4.8/5.0
Behavior5/5

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

Beyond the readOnly/idempotent/openWorld annotations, the description discloses no-API-key operation, proxy dependencies for overseas engines, server-side auto-routing behavior, searchMode semantics (auto vs. forced request/playwright), and the expectation to cite result URLs as markdown links. This is rich behavioral context that annotations alone cannot convey, and nothing contradicts the annotations.

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?

Five sentences, each carrying actionable information — purpose, mode semantics, engine guidance, citation requirement, and alternatives — with the purpose front-loaded. It is dense, but every sentence earns its place for a tool with this many routing decisions; only minor streamlining of the packed engine-guidance sentence would tighten it further.

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?

For a high-complexity tool with 6 parameters and no output schema, the description covers selection criteria, engine routing, mode behavior, proxy constraints, citation format, and the preferred alternative for official docs. The instruction to cite result URLs as markdown links tells the agent what to do with results, which compensates for the absence of an output schema.

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 high (83%), setting the baseline at 3, but the description adds genuine parameter-level value: it explains what searchMode values do ('request/playwright force that mode'), gives engine-selection semantics by language and region, and states that omitting engines triggers auto-routing. The remaining parameters (limit, queries, minResults) are already well documented in 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 opening sentence states a specific verb and resource: 'Search the web across multiple engines with no API key required.' The multi-engine and no-API-key qualifiers differentiate it clearly from the fetch-oriented siblings (fetchWebContent, fetchCsdnArticle, fetchJuejinArticle, fetchGithubReadme) and from queryDocs, which is a documentation lookup rather than a general web search.

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 gives explicit routing rules: domestic engines for Chinese queries, bing for English/official docs, proxy requirements for overseas engines, and server auto-routing when engines are omitted. It also names the preferred alternative for official documentation ('prefer resolveLibraryId + queryDocs') and provides a concrete site: operator example, so an agent knows exactly when to use this tool and when not to.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools