Skip to main content
Glama

NS Pros MCP Gateway

ms-learn__microsoft_docs_search

Search official Microsoft/Azure documentation to find the most relevant and trustworthy content for a user's query. This tool returns up to 10 high-quality content chunks (each max 500 tokens), extracted from Microsoft Learn and other official sources. Each result includes the article title, URL, and a self-contained content excerpt optimized for fast retrieval and reasoning. Always use this tool to quickly ground your answers in accurate, first-party Microsoft/Azure knowledge.

Follow-up Pat

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "ms-learn__microsoft_docs_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryNoa query or topic about Microsoft/Azure products, services, platforms, developer tools, frameworks, or APIs

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations provided, the description carries the full burden and does well: it discloses the result cap (up to 10 chunks), per-chunk size (max 500 tokens), and the shape of each result (title, URL, self-contained excerpt). It omits auth requirements, rate limits, and failure/empty-result behavior, which are the remaining gaps for an unannotated tool.

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

Conciseness3/5

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

The core is front-loaded and efficient, with the scope sentence first and the return-format details second. However, the description ends with a dangling, truncated fragment ('## Follow-up Pat'), which is dead weight and signals missing content that was cut off.

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 one-parameter search tool with no output schema, the description covers purpose, corpus, result count, chunk size, and result shape well enough to call it correctly. The truncated trailing section means the intended follow-up guidance (likely pointing at docs_fetch) is absent, leaving a small completeness gap.

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 single 'query' parameter is already documented in the schema as covering Microsoft/Azure products, services, platforms, tools, frameworks, and APIs. The description adds no syntax, formatting, or example guidance beyond that, so the baseline 3 applies.

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 description opens with a specific verb and resource ('Search official Microsoft/Azure documentation') and scopes the content to first-party Microsoft Learn sources, so an agent knows exactly what corpus is being queried. It does not explicitly contrast itself with the sibling fetch tool, so the differentiation is inferable rather than stated.

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?

'Always use this tool to quickly ground your answers in accurate, first-party Microsoft/Azure knowledge' gives a clear condition for use: answering questions that need Microsoft/Azure grounding. There are no explicit when-not-to-use conditions or named alternatives (e.g., when to switch to docs_fetch or a code-sample search), which keeps it below a 5.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.