Skip to main content
Glama
Sign In
MCP Web Search Server

MCP Web Search Server

by DmitriyOT
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

search_and_fetch

Search the web and fetch content from top results, returning combined LLM-formatted output.

Instructions

Search the web and automatically fetch content from top results. Returns combined LLM-formatted output.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "<query>"
    },
    "name": "search_and_fetch"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesSearch query
num_resultsNoNumber of results to fetch (1-20)
fetch_contentNoWhether to fetch full page content
max_content_lengthNoMax length per page

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.7/5.0
Behavior3/5

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

No annotations are provided, so the description must bear the burden. It mentions automatic fetching from 'top results' but lacks details on selection criteria, rate limits, or processing behavior.

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?

Two concise sentences efficiently convey the core functionality, though additional structure could enhance clarity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Without annotations or output schema, the description adequately explains the combined search-and-fetch process and output format, but could specify the number of top results and provide more behavioral constraints.

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% with descriptions for all 4 parameters. The description adds minimal value beyond the schema, meeting the baseline.

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 combines web search and automatic content fetching, distinguishing it from siblings 'web_search' and 'fetch_url'.

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

Usage Guidelines3/5

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

No explicit guidance on when to use this vs. alternatives; only implied by the combined nature and mention of 'LLM-formatted output'.

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