WindowsForum MCP Server

Paginated thread search

search_elastic

Read-only

Relevance-ranked full-text thread search with explicit offset pagination — use to page through a large result set beyond what the main search tool returns.

Complements the main search tool: use this to page through a large result set with an explicit offset.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`size`	No	Number of results to return (alias: limit)
`from_`	No	Offset for pagination
`limit`	No	Alias for size
`query`	Yes	Search query string
`section`	No	Part of the site to cover. Keep the default 'all' for questions and troubleshooting, so threads, news and tutorials all come back. Use 'threads', 'news' or 'tutorials' only when the user asks for that one kind of content, e.g. 'tutorials' for 'show tutorials'.	all

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 24, 2026

changedInput schema / properties / section / description

Previous value: -"Limit results to one part of the site: 'threads' (community discussions), 'news' (Windows news articles), 'tutorials' (how-to guides), or 'all'."New value: +"Part of the site to cover. Keep the default 'all' for questions and troubleshooting, so threads, news and tutorials all come back. Use 'threads', 'news' or 'tutorials' only when the user asks for that one kind of content, e.g. 'tutorials' for 'show tutorials'."

Changed1 schema field changedSep 22, 2026

addedInput schema / properties / section

Added value: +{
+  "default": "all",
+  "description": "Limit results to one part of the site: 'threads' (community discussions), 'news' (Windows news articles), 'tutorials' (how-to guides), or 'all'.",
+  "enum": [
+    "all",
+    "threads",
+    "news",
+    "tutorials"
+  ],
+  "type": "string"
+}

First observedJul 12, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false. The description adds useful behavioral context: the search is relevance-ranked, full-text, and uses explicit offset pagination. It goes beyond the annotations but does not address aspects like result limits or response shape, though an output schema exists.

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?

The description is short and front-loaded with the core purpose. However, the phrase 'use to page through a large result set' appears twice in slightly different forms, creating minor redundancy. Still, every sentence earns its place and it remains efficient.

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?

Given the output schema and complete parameter descriptions, the tool is adequately specified. The description clarifies when to choose it over the main `search` tool and communicates the pagination model. It does not explain distinctions from other search variants like `search_mysql` or `search_semantic`, but those are not required for basic correct invocation.

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 100%, so the parameters are already fully documented. The description adds no syntax details beyond what the schema provides, but the pagination and relevance-ranking hints align with the `from_`/`size` and `query` parameters. Baseline 3 is appropriate.

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 and resource: 'Relevance-ranked full-text thread search with explicit offset pagination'. It clearly distinguishes this tool from the main `search` tool by emphasizing pagination and large result sets, which is reinforced by the title 'Paginated thread search'.

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?

It explicitly says when to use this tool: 'use to page through a large result set beyond what the main search tool returns'. It names the alternative `search` tool and gives a concrete condition, making the routing decision unambiguous.

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

All WindowsForum MCP Server tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?