Skip to main content
Glama

WindowsForum MCP Server

by com.windowsforum
OverviewDiscussionsAdmin

Exact title/author lookup

search_mysql
Read-only

Exact substring lookup over thread titles and author usernames, ordered by view count — use for literal title or author matching rather than relevance-ranked full-text search.

Complements the main search tool: use this for literal title or author matching rather than relevance-ranked full-text search.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum number of results to return
queryYesLiteral text to match against thread titles and author usernames
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

A3.9/5.0
Behavior4/5

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

Annotations already provide readOnlyHint=true and destructiveHint=false, lowering the burden. The description adds useful behavioral context: matching is exact substring, and results are ordered by view count. It does not mention pagination or rate limits, but for a read-only search tool with an output schema this is sufficient additional disclosure.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The first sentence conveys the full substance: exact substring lookup, target fields, ordering, and the contrast with relevance-ranked search. The second sentence repeats the same 'literal vs relevance-ranked' contrast and the relationship to `search`, adding no new information. This redundancy means not every sentence earns its place.

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 100% schema coverage, safe read-only annotations, and presence of an output schema, the description provides adequate context: what is searched, matching semantics, ordering, and when to prefer this tool over `search`. Nothing critical for correctly invoking the tool appears to be missing.

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%, and the schema already provides rich, self-explanatory descriptions for `query`, `limit`, and `section`. The tool description's mention of exact substring matches `query` and adds no parameter-level meaning beyond what the schema already documents. Baseline 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 states a specific operation ('Exact substring lookup over thread titles and author usernames'), names the ordering ('ordered by view count'), and contrasts itself with relevance-ranked full-text search. This makes its purpose immediately clear and distinguishes it from the sibling `search` tool without needing to inspect schemas.

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?

The description explicitly says to use this tool for literal title/author matching rather than relevance-ranked full-text search and names `search` as the complementary alternative. It is clear about the primary decision, though it does not distinguish from other search siblings like `search_threads` or `search_users`. The core usage guidance is present.

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