search-boost-mcp

Overview Schema Source Related Servers Discussions Admin

Fused Web Search

fused_search

Read-only

Run multi-engine web research for precise lookups or complex investigations, returning ranked extracts, source attribution, and diagnostics.

Instructions

Use for the vast majority of public-web research tasks, from precise lookups to difficult investigations. This general-purpose multi-engine search does not require Jev. If adaptive_search is unavailable, disabled or Jev is not configured, use enabled fused_search normally; do not delay research or require Jev setup. When both tools are available, choose fused_search for direct retrieval, varied query angles or explicit source control. Prefer adaptive_search for higher-quality intent-guided evidence selection when a medium-to-high difficulty or uncertain question benefits from screening noisy or mixed-relevance results. Choose by the evidence need, not merely by which tools are configured. Returns ranked extracts, source attribution and execution diagnostics, including failures and warnings. Normally omit engines; request-local choices do not change persistent defaults. Add X community voices when relevant; use x_search for X-only tasks. Scores do not verify claims, and multiple engines finding the same page do not independently corroborate it. Use fetch_page to read decisive sources when extracts are insufficient. Optional live status: search-boost://capabilities Resource.

Input Schema

TableJSON Schema

Name	Required	Description
`layer`	No	Deprecated compatibility alias: free→free pool, api→hybrid pool; engine_pool takes precedence; not persisted
`query`	Yes	Search query (site:, -site:, "phrase", A OR B)
`engines`	No	Optional exact engine selection overriding engine_pool; unavailable or disabled engines are skipped with warnings
`queries`	No	Distinct query angles, not paraphrases; complexity caps total variants at 1/2/3, including query and OR alternatives
`ranking`	No	Final engine-weight preset only; default balanced
`recency`	No	Favor recent dated results; omit for historical or version-pinned documentation
`community`	No	Add X developer/community voices when relevant; default false; shares final max_results
`min_score`	No	Minimum consensus-v2 quality score; old thresholds need recalibration, default 0
`complexity`	No	Budget, query variants and depth only; default medium
`engine_pool`	No	Which engines to search. Omitted: compatibility layer free→free, api→hybrid
`max_results`	No	Max results (default 6)
`engine_weights`	No	Override preset engine weights; zero still calls the engine. Never enables or selects engines
`exclude_domains`	No	Exclude these hostnames from results
`include_domains`	No	Restrict results to these hostnames, e.g. nodejs.org; useful for official sources

Output Schema

TableJSON Schema

Name	Required	Description	Default
`tier`	Yes
`layer`	Yes
`query`	Yes
`tookMs`	Yes
`ranking`	Yes
`results`	Yes
`cacheHit`	Yes
`warnings`	No
`enginePool`	Yes
`engineStats`	No
`enginesUsed`	No
`resultCount`	Yes
`scoreVersion`	Yes
`communityUsed`	Yes
`effectiveWeights`	Yes
`enginesRequested`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv0.2.4Oct 3, 2026

changedInput schema / properties / engine_weights / description

Previous value: -"Override preset engine weights; never enables or selects engines"New value: +"Override preset engine weights; zero still calls the engine. Never enables or selects engines"

changedInput schema / properties / queries / description

Previous value: -"Distinct query angles, not paraphrases; use up to 3 variants"New value: +"Distinct query angles, not paraphrases; complexity caps total variants at 1/2/3, including query and OR alternatives"

Changed37 schema fields changedv0.2.2Sep 22, 2026

addedInput schema / properties / community

Added value: +{
+  "description": "Add X developer/community voices when relevant; default false; shares final max_results",
+  "type": "boolean"
+}

addedInput schema / properties / complexity / description

Added value: +"Budget, query variants and depth only; default medium"

changedInput schema / properties / complexity / enum

Previous value: -[
-  "auto",
-  "simple",
-  "medium",
-  "complex"
-]New value: +[
+  "simple",
+  "medium",
+  "complex"
+]

addedInput schema / properties / engine_pool

Added value: +{
+  "description": "Which engines to search. Omitted: compatibility layer free→free, api→hybrid",
+  "enum": [
+    "free",
+    "api",
+    "hybrid"
+  ],
+  "type": "string"
+}

addedInput schema / properties / engine_weights

Added value: +{
+  "additionalProperties": false,
+  "description": "Override preset engine weights; never enables or selects engines",
+  "properties": {
+    "anysearch": {
+      "minimum": 0,
+      "type": "number"
+    },
+    "bing": {
+      "minimum": 0,
+      "type": "number"
+    },
+    "brave": {
+      "minimum": 0,
+      "type": "number"
+    },
+    "ddg": {
+      "minimum": 0,
+      "type": "number"
+    },
+    "exa": {
+      "minimum": 0,
+      "type": "number"
+    },
+    "exa-free": {
+      "minimum": 0,
+      "type": "number"
+    },
+    "tavily": {
+      "minimum": 0,
+      "type": "number"
+    },
+    "yahoo": {
+      "minimum": 0,
+      "type": "number"
+    }
+  },
+  "type": "object"
+}

changedInput schema / properties / engines / description

Previous value: -"Engine subset override"New value: +"Optional exact engine selection overriding engine_pool; unavailable or disabled engines are skipped with warnings"

changedInput schema / properties / engines / items / enum

Previous value: -[
-  "bing",
-  "ddg",
-  "yahoo",
-  "exa-free",
-  "antigravity",
-  "tavily",
-  "brave",
-  "exa"
-]New value: +[
+  "bing",
+  "ddg",
+  "yahoo",
+  "exa-free",
+  "anysearch",
+  "tavily",
+  "brave",
+  "exa"
+]

addedInput schema / properties / engines / minItems
```
Added value: +1
```
addedInput schema / properties / exclude_domains / description
```
Added value: +"Exclude these hostnames from results"
```

addedInput schema / properties / include_domains / description

Added value: +"Restrict results to these hostnames, e.g. nodejs.org; useful for official sources"

addedInput schema / properties / layer / description

Added value: +"Deprecated compatibility alias: free→free pool, api→hybrid pool; engine_pool takes precedence; not persisted"

addedInput schema / properties / min_score

Added value: +{
+  "description": "Minimum consensus-v2 quality score; old thresholds need recalibration, default 0",
+  "minimum": 0,
+  "type": "number"
+}

changedInput schema / properties / queries / description

Previous value: -"Extra query variants (max 3)"New value: +"Distinct query angles, not paraphrases; use up to 3 variants"

addedInput schema / properties / ranking

Added value: +{
+  "description": "Final engine-weight preset only; default balanced",
+  "enum": [
+    "balanced",
+    "research",
+    "fresh"
+  ],
+  "type": "string"
+}

addedInput schema / properties / recency / description

Added value: +"Favor recent dated results; omit for historical or version-pinned documentation"

addedOutput schema / properties / communityUsed
```
Added value: +{
+  "type": "boolean"
+}
```

addedOutput schema / properties / effectiveWeights

Added value: +{
+  "additionalProperties": {
+    "type": "number"
+  },
+  "type": "object"
+}

addedOutput schema / properties / enginePool

Added value: +{
+  "enum": [
+    "free",
+    "api",
+    "hybrid"
+  ],
+  "type": "string"
+}

addedOutput schema / properties / engineStats / additionalProperties / properties / attempts
```
Added value: +{
+  "type": "number"
+}
```
addedOutput schema / properties / engineStats / additionalProperties / properties / successes
```
Added value: +{
+  "type": "number"
+}
```

addedOutput schema / properties / ranking

Added value: +{
+  "enum": [
+    "balanced",
+    "research",
+    "fresh"
+  ],
+  "type": "string"
+}

addedOutput schema / properties / results / items / properties / consensusBoost
```
Added value: +{
+  "type": "number"
+}
```

addedOutput schema / properties / results / items / properties / contributions

Added value: +{
+  "additionalProperties": {
+    "type": "number"
+  },
+  "type": "object"
+}

addedOutput schema / properties / results / items / properties / dateStatus

Added value: +{
+  "enum": [
+    "known",
+    "unknown",
+    "conflicting"
+  ],
+  "type": "string"
+}

addedOutput schema / properties / results / items / properties / engineRanks

Added value: +{
+  "additionalProperties": {
+    "type": "number"
+  },
+  "type": "object"
+}

addedOutput schema / properties / results / items / properties / evidenceScore
```
Added value: +{
+  "type": "number"
+}
```
addedOutput schema / properties / results / items / properties / id
```
Added value: +{
+  "type": "string"
+}
```

addedOutput schema / properties / results / items / properties / kind

Added value: +{
+  "enum": [
+    "web",
+    "x"
+  ],
+  "type": "string"
+}

addedOutput schema / properties / results / items / properties / metadataDelta
```
Added value: +{
+  "type": "number"
+}
```

addedOutput schema / properties / results / items / properties / provenance

Added value: +{
+  "items": {
+    "additionalProperties": false,
+    "properties": {
+      "engine": {
+        "type": "string"
+      },
+      "published": {
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "rank": {
+        "type": "number"
+      },
+      "snippet": {
+        "type": "string"
+      },
+      "title": {
+        "type": "string"
+      },
+      "url": {
+        "type": "string"
+      },
+      "variant": {
+        "type": "string"
+      }
+    },
+    "required": [
+      "engine",
+      "rank",
+      "url",
+      "title",
+      "snippet",
+      "published"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}

addedOutput schema / properties / results / items / properties / rankScore
```
Added value: +{
+  "type": "number"
+}
```
addedOutput schema / properties / results / items / properties / scoreVersion
```
Added value: +{
+  "type": "string"
+}
```
addedOutput schema / properties / results / items / properties / selectionScore
```
Added value: +{
+  "type": "number"
+}
```
addedOutput schema / properties / results / items / properties / username
```
Added value: +{
+  "type": "string"
+}
```

changedOutput schema / properties / results / items / required

Previous value: -[
-  "title",
-  "url",
-  "domain",
-  "snippet",
-  "score",
-  "engines",
-  "published"
-]New value: +[
+  "title",
+  "url",
+  "domain",
+  "snippet",
+  "score",
+  "scoreVersion",
+  "rankScore",
+  "evidenceScore",
+  "consensusBoost",
+  "metadataDelta",
+  "engineRanks",
+  "contributions",
+  "provenance",
+  "dateStatus",
+  "engines",
+  "published"
+]

addedOutput schema / properties / scoreVersion
```
Added value: +{
+  "type": "string"
+}
```

changedOutput schema / required

Previous value: -[
-  "query",
-  "layer",
-  "tier",
-  "tookMs",
-  "cacheHit",
-  "resultCount",
-  "results"
-]New value: +[
+  "scoreVersion",
+  "query",
+  "layer",
+  "tier",
+  "tookMs",
+  "cacheHit",
+  "resultCount",
+  "enginePool",
+  "ranking",
+  "effectiveWeights",
+  "communityUsed",
+  "results"
+]

Changed4 schema fields changedv0.1.6Aug 19, 2026

addedOutput schema / properties / engineStats

Added value: +{
+  "additionalProperties": {
+    "additionalProperties": false,
+    "properties": {
+      "errors": {
+        "type": "number"
+      },
+      "note": {
+        "type": "string"
+      },
+      "used": {
+        "type": "boolean"
+      }
+    },
+    "required": [
+      "used",
+      "errors"
+    ],
+    "type": "object"
+  },
+  "type": "object"
+}

addedOutput schema / properties / enginesRequested

Added value: +{
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

addedOutput schema / properties / enginesUsed

Added value: +{
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

addedOutput schema / properties / warnings

Added value: +{
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

First observedv0.1.2Aug 17, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations already cover the safety profile (readOnlyHint, openWorldHint, non-destructive), and the description adds substantial behavior beyond them: returns ranked extracts plus source attribution and execution diagnostics including failures/warnings, scores do not verify claims, agreement across engines is not independent corroboration, request-local choices do not alter persistent defaults, and disabled engines are skipped with warnings.

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 primary use case and the routing decision, and most sentences carry distinct information. However, it runs long and contains mild redundancy, e.g. 'do not delay research or require Jev setup' restates the preceding clause and 'choose by the evidence need' restates the routing rule already given.

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 14-parameter tool with nested objects, enums, and an output schema, the description covers routing, fallbacks, parameter defaults, return contents, and caveats about interpreting results. Nothing an agent needs to invoke it correctly is missing.

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. The description still adds non-obvious meaning: engines should normally be omitted, request-local selections are not persisted, community adds X voices and shares the final max_results budget, and engine_pool takes precedence over the deprecated layer alias.

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 verb and resource ('general-purpose multi-engine search') and explicitly distinguishes itself from siblings: x_search for X-only tasks, fetch_page for reading decisive sources, and adaptive_search for intent-guided evidence selection. An agent can route between these without opening a 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?

Explicit when-to-use ('vast majority of public-web research tasks', 'direct retrieval, varied query angles or explicit source control'), explicit when-to-prefer-the-alternative (adaptive_search for medium-to-high difficulty or noisy results), and explicit fallback behavior if Jev is unavailable. The selection criterion is stated as a principle ('choose by the evidence need') rather than left to inference.

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

Deploy Server