Skip to main content
Glama
Tiberriver256

Azure DevOps MCP Server

by Tiberriver256
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

search_wiki

Search Azure DevOps wiki pages in a project to find content by text, with filtering and pagination.

Instructions

Search for content across wiki pages in a project

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
topYesNumber of results to return (default: 100, max: 1000)
skipYesNumber of results to skip for pagination (default: 0)
filtersNoOptional filters to narrow search results
projectIdNoThe ID or name of the project to search in. If omitted, the search runs across the organization when supported.
searchTextYesThe text to search for in wikis
includeFacetsYesWhether to include faceting in results (default: true)
organizationIdNoThe ID or name of the organization (Default: mycompany)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.0.6
    • addedInput schema / properties / skip / maximum
      Added value: +9007199254740991
    • changedInput schema / required
      Previous value: -[
-  "searchText"
-]New value: +[
+  "searchText",
+  "top",
+  "skip",
+  "includeFacets"
+]
  2. Changed1 schema field changedv0.1.10
    • changedInput schema / properties / projectId / description
      Previous value: -"The ID or name of the project to search in (Default: MyProject). If not provided, the default project will be used."New value: +"The ID or name of the project to search in. If omitted, the search runs across the organization when supported."
  3. Changed3 schema fields changedv1.0.0
    • addedInput schema / properties / organizationId
      Added value: +{
+  "description": "The ID or name of the organization (Default: mycompany)",
+  "type": "string"
+}
    • changedInput schema / properties / projectId / description
      Previous value: -"The ID or name of the project to search in"New value: +"The ID or name of the project to search in (Default: MyProject). If not provided, the default project will be used."
    • changedInput schema / required
      Previous value: -[
-  "searchText",
-  "projectId"
-]New value: +[
+  "searchText"
+]
  4. First observed

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It reveals nothing about pagination behavior (despite top/skip parameters), result ordering, relevance, authentication requirements, or any other operational trait beyond the basic search action.

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?

The description is a single, front-loaded sentence with zero waste. It efficiently conveys the core action and scope without unnecessary detail.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool with 7 parameters, nested filters, no output schema, and no annotations, the description is too thin. It does not mention that projectId is optional (allowing organization-wide search) or that pagination and faceting are available, leaving the agent to rely entirely on the schema for critical context.

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%, so the schema already documents all parameters thoroughly. The description adds no parameter-level meaning, which is acceptable given the high coverage, but it does not compensate for any gaps.

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 states a specific verb ('Search') and resource ('wiki pages'), and specifies scope ('in a project'), making it clear what the tool does. It implicitly distinguishes from siblings like search_code and search_work_items by specifying 'wiki pages', but does not explicitly name alternatives.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives such as list_wiki_pages or get_wiki_page, nor does it mention any prerequisites or conditions. It only states what the tool does, leaving usage entirely to inference.

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

Deploy Server

Other Tools