Skip to main content
Glama
lhswgzy

free-search-mcp-ts

by lhswgzy
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Research a question (search + read + organise)

research
Read-only

Runs a full web search and retrieval loop: queries multiple engines, expands terms, fetches and quotes passages from relevant sources, and returns a citable Markdown brief.

Instructions

One call that does the whole mechanical research loop: search several engines, derive extra queries from the vocabulary of the results, fetch the most relevant and diverse sources, then extract the passages from each that actually answer the question. Returns a Markdown brief with numbered, citable sources and verbatim quoted passages — it does NOT paraphrase, because this server has no language model; you write the synthesis from the evidence it gathers. Use this instead of chaining web_search and several fetch_url calls whenever you need more than a snippet. depth 1 = the query as written. depth 2 (default) = the query plus expansions derived from what the first page of results is actually about. depth 3 = broader expansion and more sources.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
depthNoHow hard to dig. 1 is fastest, 3 is most thorough (default 2).
queryYesThe research question, in natural language.
formatNoOutput format. "markdown" (default) is compact and readable; "json" returns structured data for post-processing.
regionNoRegion hint such as "us" or "cn".
enginesNoEngines to use, in priority order. Omit for automatic tiered selection (keyless defaults first, then fallbacks, then matching subject indexes). Use ["all"] for every configured engine, or see the list_engines tool for ids.
refreshNoIgnore cached pages and re-fetch every source (default false).
languageNoLanguage hint such as "en" or "zh".
freshnessNoOnly return results newer than this. Honoured by engines that support it (Google News, Bing, Serper, Tavily, Brave, Google CSE) and ignored by the rest.
max_sourcesNoHow many sources to fetch and quote (default 8 at depth 2+).
safe_searchNoSafe-search level. Defaults to the server configuration ("moderate").
exclude_domainsNoExclude these domains from the research.
include_domainsNoRestrict the research to these domains.
passages_per_sourceNoPassages to quote per source (default 4).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already declare readOnlyHint/openWorldHint, but the description adds behavior annotations cannot: the server has no language model, so it does NOT paraphrase and the agent must write the synthesis itself. It also describes the actual return shape (verbatim passages, numbered citable sources), which is critical given there is no output schema.

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?

Front-loaded with the pipeline and clear value; every clause carries signal. Slightly long, and the depth elaboration partly overlaps the schema, but nothing is wasted filler.

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?

With no output schema, the description carries the full burden of explaining return values and does so (Markdown brief, numbered sources, verbatim quotes, markdown vs json formats). It also flags the key limitation (no LLM synthesis server-side), so an agent knows exactly what it must do next.

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% so the baseline is 3, but the description earns above baseline by elaborating what depth actually does ('depth 2 = the query plus expansions derived from what the first page of results is actually about'), which the terse schema ('How hard to dig') does not convey.

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?

States a specific compound action (search several engines, expand queries, fetch sources, extract answering passages) and names the exact output artifact (a Markdown brief with numbered citable sources and verbatim quotes). An agent can distinguish this from web_search or fetch_url without opening any schema.

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 routes the agent: 'Use this instead of chaining web_search and several fetch_url calls whenever you need more than a snippet' — naming the alternatives and the condition ('more than a snippet') that selects this tool. It also gives depth-tier guidance so the agent knows which intensity to pick.

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