Skip to main content
Glama
websearch-mcp

websearch-mcp

by xronocode

search_semantic

Read-onlyIdempotent

Run semantic web searches for meaning-style research queries where keyword search misses, with neural engine fallback and cached results.

Instructions

Free LOCAL semantic/neural web search. Use for meaning-style research queries — 'articles about X', 'how companies solve Y', solution discovery — where keyword search misses. Route: Exa (neural) -> Tavily -> ddgs fallback; Exa/Tavily join only when their keys are installed (~/.config/websearch-mcp/exa.key / tavily.key). Returns title, URL, snippet, date and an [engine: ...] tag. Cached 24h.

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

Input Schema

NameRequiredDescriptionDefault
queryYes
max_resultsNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.1

TDQS

A4.4/5.0
Behavior5/5

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

Beyond the annotations (readOnly/openWorld/idempotent/non-destructive), the description discloses the engine routing chain, the conditional join of Exa/Tavily based on installed key files, a graceful ddgs fallback, the returned fields, and a 24h cache TTL that tells the agent results may be stale. That is significant behavioral context an agent cannot get from 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Four tight sentences, front-loaded with purpose, then usage, then routing, then return shape. The telegraphic "Route: Exa -> Tavily -> ddgs" line is dense but unambiguous and earns its space.

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?

An output schema exists so return values did not need spelling out, yet the description lists them anyway; caching and fallback behavior cover the main operational surprises. Minor gaps remain around result quality/rate behavior when falling back to ddgs, but nothing an agent needs before calling is missing.

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 description coverage is 0%, so the description carries the burden for both parameters. It conveys that `query` should be phrased as a natural-language meaning query, but `max_results` receives no mention at all — no default rationale or guidance on result count.

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 states a specific verb+resource combination ("semantic/neural web search") and immediately scopes it against keyword search, which is exactly the axis an agent needs to distinguish this from the sibling `search` tool. Local/free execution is also declared up front.

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?

It gives concrete when-to-use criteria — meaning-style research queries, 'articles about X', 'how companies solve Y', solution discovery — plus the negative condition "where keyword search misses." It stops short of naming `search` or `search_news` as the explicit alternative, so the routing is implied rather than stated.

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