search-boost-mcp

Overview Schema Source Related Servers Discussions Admin

Search Stats

search_stats

Read-only

Inspect read-only search diagnostics to review cache activity, engine configuration readiness, recent searches, and result warnings before troubleshooting empty or missing results.

Instructions

Read-only search diagnostics: cache activity, engine configuration readiness and recent searches. Inspect result warnings as well; empty results do not prove absence or authorize changing credentials, permissions or defaults.

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON Schema

Name	Required	Description	Default
`layer`	Yes
`recent`	Yes
`engines`	Yes
`xSource`	Yes
`cacheHits`	Yes
`startedAt`	Yes
`xOfficial`	Yes
`tierCounts`	Yes
`cacheMisses`	Yes
`keyedEngines`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv0.2.2Sep 22, 2026

addedOutput schema / properties / keyedEngines

Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "configured": {
+      "type": "number"
+    },
+    "enabled": {
+      "type": "number"
+    },
+    "enabledNames": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "total": {
+      "type": "number"
+    }
+  },
+  "required": [
+    "configured",
+    "enabled",
+    "total",
+    "enabledNames"
+  ],
+  "type": "object"
+}

changedOutput schema / required

Previous value: -[
-  "startedAt",
-  "layer",
-  "cacheHits",
-  "cacheMisses",
-  "tierCounts",
-  "engines",
-  "xOfficial",
-  "xSource",
-  "recent"
-]New value: +[
+  "startedAt",
+  "layer",
+  "cacheHits",
+  "cacheMisses",
+  "tierCounts",
+  "keyedEngines",
+  "engines",
+  "xOfficial",
+  "xSource",
+  "recent"
+]

First observedv0.1.2Aug 17, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint=true, destructiveHint=false), so the bar is lower. The description adds genuine value beyond them: it discloses the diagnostic surfaces returned and warns that empty results do not authorize changing credentials, permissions, or defaults — a meaningful behavioral caveat for an agent acting on ambiguous results.

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 front-loaded sentences: the first defines scope, the second carries the caution. No filler, though the second sentence packs three distinct warnings and is slightly dense.

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?

An output schema exists, so return values need not be described. With zero parameters and annotations covering the safety profile, the description supplies everything an agent needs to call this correctly, including the caveat about interpreting empty results.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate. Baseline of 4 applies; the description neither helps nor hurts parameter understanding.

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?

The description names a concrete resource and enumerates what it exposes: cache activity, engine configuration readiness, and recent searches. It clearly reads as a diagnostics tool, distinct from the search/retrieval siblings (fused_search, fetch_page, search_layer), though it never names an alternative explicitly.

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?

It gives interpretive guidance ('inspect result warnings', 'empty results do not prove absence') but never states when to call this tool versus the search siblings or when not to. Usage is implied by the diagnostics framing rather than spelled out.

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

Deploy Server