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, replies, or views, in either order, with pagination; use when result ordering or paging matters.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sizeNoNumber of results to return
from_NoOffset for pagination
orderNoSort order (asc, desc)desc
queryYesSearch query string
sortbyNoSort field (relevance, date, replies, views)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 / 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'."
  2. 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"
+}
  3. First observed

TDQS

A4/5.0
Behavior3/5

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

Annotations already mark readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds only the structured sort/pagination behavior, which is useful but does not go beyond what one would expect from a read-only search tool.

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?

A single front-loaded sentence states the verb, resource, key options, and usage trigger with no filler. It earns its place and is easy to scan.

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?

For a read-only search tool with an output schema and fully described parameters, the description is largely complete. It could strengthen sibling differentiation among the many search_* tools, but the core selection and usage information is present.

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 coverage is 100%, and the schema descriptions already define sortby values, order, size, from_, and section. The description's mention of sorting and pagination maps to those parameters without adding new parameter-level meaning, so the baseline of 3 applies.

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 names a specific verb ('Search'), a specific resource (WindowsForum threads), and its distinguishing capability (sorting by relevance, date, replies, or views with pagination). This differentiates it clearly from siblings like search_posts or the generic search tools.

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 explicitly states when to use this tool: 'use when result ordering or paging matters.' It does not name alternatives or state when not to use it, but the positive trigger is clear and actionable.

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