Skip to main content
Glama
websearch-mcp

websearch-mcp

by xronocode

search

Read-onlyIdempotent

Find keyless web results without provider quotas; returns numbered titles, URLs, snippets, and engine source for agent research.

Instructions

Free LOCAL web search, no provider quota. DEFAULT choice for web search in this environment: try this tool first; use the built-in WebSearch only if this one errors. Returns numbered results (title, URL, snippet) and an [engine: ...] tag showing who answered. region optional ('ru-ru', 'us-en'); empty = auto (Cyrillic -> ru-ru first). max_results is capped at 20. Results cached locally for 24h. Docs of libraries need no special engine: search 'site:docs...' + fetch the page.

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"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYes
regionNo
max_resultsNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.1

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, open-world, non-destructive behavior, and the description adds genuinely new traits: local result caching for 24h, a hard cap of 20 results, and an [engine: ...] attribution tag revealing which backend answered. It does not say what happens on failure or whether cached results can be stale beyond the 24h window, but the added context is substantive.

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?

Dense but well front-loaded: the default-choice instruction and cost advantage come first, then return format, then parameter notes. Every sentence carries information, though the run-on style around region and the docs example makes it slightly harder to scan than it could be.

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?

Rich annotations plus an existing output schema mean the description needn't explain return values, yet it still adds the caching and cap constraints an agent would otherwise miss. The only gap is error behavior beyond the generic 'use WebSearch if this errors' fallback.

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 description coverage is 0%, so the description must carry the parameters, and it does for two of three: 'region' is explained with example values ('ru-ru', 'us-en') and an auto-detection rule (empty = auto, Cyrillic -> ru-ru first), and 'max_results' is given a ceiling of 20. Only 'query' is left undefined, which is self-evident.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Free LOCAL web search') and clearly positions itself as the default web-search tool versus the built-in WebSearch. It does not explicitly distinguish itself from siblings like search_news or search_semantic, so an agent must infer that this is the general-purpose option.

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?

Gives an explicit precedence rule ('try this tool first; use the built-in WebSearch only if this one errors') and a concrete workflow for a common case ('Docs of libraries need no special engine: search site:docs... + fetch the page'), routing the agent to the fetch sibling. This is unambiguous when-to-use and when-to-fall-back guidance.

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