Skip to main content
Glama

WindowsForum MCP Server

by com.windowsforum
OverviewDiscussionsAdmin

Search threads (sortable)

search_threads
Read-only

Search WindowsForum threads with structured controls — sort by relevance, date, views or replies, in either order, with pagination; use when result ordering or paging matters. Latest/newest requests replace the default relevance sort with date order; a query such as 'latest tutorials' lists that section without requiring those words in the content. Views/replies sort the complete indexed matching corpus inside a frozen snapshot; they require a complete, fresh popularity index. Counts shown for these sorts come from that index snapshot, with a conservative counts_as_of freshness watermark. Ranking metadata identifies an applied database transaction barrier or a rolling metadata sweep. Native view totals are source-aggregated on approximately a 15-minute cadence, so recent visits and subsequent source changes may not yet be reflected. For popularity continuation pass next_cursor as cursor, leaving from_=0; cursors are short-lived (well under two minutes), so page promptly and start again from the first page if one has expired. The total is exact when total_relation is 'eq', otherwise a verified public lower bound ('gte'); use has_more and next_from to continue. If pagination_limited is true, narrow the query or section instead of paging further.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sizeNoNumber of results to return
from_NoContinuation offset: the number of results already shown. Pass next_from from the previous page.
orderNoSort order (asc, desc)desc
queryYesSearch query string
cursorNoPopularity-only continuation token from next_cursor; reuse the same query, section and sort
sortbyNoSort field (relevance, date, views, replies)relevance
sectionNoPart 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
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / from_ / description
      Previous value: -"Continuation offset; pass next_from instead of adding the result count. Keyword search uses index-candidate offsets; newest listings use visible-row offsets, identified by pagination_mode."New value: +"Continuation offset: the number of results already shown. Pass next_from from the previous page."
  2. Changed2 schema fields changed
    • addedInput schema / properties / cursor
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Popularity-only continuation token from next_cursor; reuse the same query, section and sort"
+}
    • changedInput schema / properties / sortby / description
      Previous value: -"Sort field (relevance, date)"New value: +"Sort field (relevance, date, views, replies)"
  3. Changed2 schema fields changed
    • changedInput schema / properties / from_ / description
      Previous value: -"Offset for pagination"New value: +"Continuation offset; pass next_from instead of adding the result count. Keyword search uses index-candidate offsets; newest listings use visible-row offsets, identified by pagination_mode."
    • changedInput schema / properties / sortby / description
      Previous value: -"Sort field (relevance, date, replies, views)"New value: +"Sort field (relevance, date)"
  4. Changed1 schema field changed
    • 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'."
  5. Changed1 schema field changed
    • 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"
+}
  6. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Annotations already declare read-only/safe/closed-world, yet the description adds substantial non-obvious behavior: short-lived cursors (<2 min), the frozen popularity snapshot, source-aggregated ~15-minute view cadence, total_relation semantics, and pagination_limited handling. This is real operational context an agent cannot get from the structured fields.

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 purpose and the 'use when' clause are front-loaded, and most sentences carry actionable information. It is dense and leans on internal jargon ('database transaction barrier', 'rolling metadata sweep') that may not help an agent, keeping it just below the top mark.

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 7-parameter search tool with a full output schema and safe annotations, the description covers the remaining gaps: ordering overrides, cursor lifetime, count freshness/watermarks, total_relation bounds, and how to react to pagination_limited. Nothing essential to calling 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, but the description genuinely extends the schema: it explains the popularity continuation flow (pass next_cursor as cursor with from_=0, same query/section/sort), the latest/newest override of relevance sort, and the practical meaning of order/sortby combinations.

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 opening states a specific verb+resource ('Search WindowsForum threads') and enumerates the sortable dimensions and pagination, so the agent knows exactly what this does. It does not, however, distinguish itself from the many sibling search tools (search, search_posts, search_semantic, search_elastic), leaving that routing to the tool name alone.

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 a clear when-to-use signal ('use when result ordering or paging matters') plus concrete query-pattern guidance ('latest tutorials' lists that section without requiring those words). It stops short of naming alternative tools or stating when-not to use it, so it is context-rich but not a full routing guide.

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 toolsInspect
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