Skip to main content
Glama

WindowsForum MCP Server

by com.windowsforum
OverviewDiscussionsAdmin

Show search results

render_search_results
Read-only

Show WindowsForum threads, news articles, tutorials or posts to the user as a result card, grouped by section. Call search or list_threads first, pick the results that answer the request (keep their order), then pass their ids here; the card displays each item's title, snippet, author, date, and link.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idsYesDocument ids to show, in display order, e.g. ['thread-430404', 'post-991595'] — the `id` values returned by search, list_threads, search_semantic, search_threads, search_posts, or search_elastic.
queryNoThe user's request, shown as the card's heading, e.g. 'BitLocker recovery key after update' or 'Latest tutorials'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / ids / description
      Previous value: -"Document ids to show, in display order, e.g. ['thread-430404', 'post-991595'] — the `id` values returned by search, search_semantic, search_threads, search_posts, or search_elastic."New value: +"Document ids to show, in display order, e.g. ['thread-430404', 'post-991595'] — the `id` values returned by search, list_threads, search_semantic, search_threads, search_posts, or search_elastic."
    • changedInput schema / properties / query / description
      Previous value: -"The search the user asked for, shown as the card's heading."New value: +"The user's request, shown as the card's heading, e.g. 'BitLocker recovery key after update' or 'Latest tutorials'."
  2. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -{
-  "additionalProperties": true,
-  "type": "object"
-}New value: +null
  3. Added

TDQS

A4.4/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, so the safety profile is covered. The description adds meaningful behavioral detail: it renders a card grouped by section, displays title, snippet, author, date, and link, and preserves the order of passed ids. This is beyond the annotations and helps the agent understand the output behavior.

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?

Three sentences with no fluff. Purpose is front-loaded, workflow follows logically, and the display details are concise. 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?

For a rendering tool with read-only annotations and no output schema, the description covers the main workflow, display contents, and ordering. It could mention what happens with invalid ids or explicitly state it does not search, but the 'call search first' instruction covers that. Overall complete for the agent's needs.

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 both parameters have clear descriptions. The description reinforces the ids parameter as document ids to display and mentions order preservation, but adds little beyond the schema. It also references the query as the card heading, which is already in the schema. Baseline of 3 is appropriate given high schema coverage.

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?

Description states a specific verb ('Show') and resource (threads, news, tutorials, posts as a result card), and implicitly distinguishes from sibling render tools like render_thread and render_kb_article by focusing on a grouped result card. It clearly conveys what the tool does.

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?

Explicitly prescribes the workflow: call search or list_threads first, select relevant results, preserve order, then pass ids. This gives clear when-to-use guidance and implies it is for displaying multiple search results, not for individual rendering. It names the prerequisite tools directly.

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