Skip to main content
Glama
Tiberriver256

Azure DevOps MCP Server

by Tiberriver256
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

search_code

Search code across Azure DevOps project repositories by text and filter results by repository, branch, path, or code element to locate matching files and snippets.

Instructions

Search for code across repositories 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 (Default: MyProject). If not provided, the default project will be used.
searchTextYesThe text to search for
includeContentYesWhether to include full file content in results (default: true)
includeSnippetYesWhether to include code snippets 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",
+  "includeSnippet",
+  "includeContent"
+]
  2. 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"
+]
  3. First observed

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden, but it only says 'Search for code.' It does not disclose that this is a read-only operation, how pagination works, whether results include content or snippets by default, or any permission or rate-limit context.

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

Conciseness4/5

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

The description is a single front-loaded sentence with no filler. It is concise and structurally sound, though it may be too terse for an 8-parameter tool with nested filters.

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 an 8-parameter tool with a nested filters object, no output schema, and no annotations, the description is incomplete. It omits return format, pagination behavior, filter capabilities, and default project/organization behavior, leaving the agent without important 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 all parameter meanings are already documented in the input schema. The description adds no parameter-level detail beyond what the schema provides, making the baseline score of 3 appropriate.

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?

States a specific verb ('Search'), resource ('code'), and scope ('across repositories in a project'), so the agent knows this is a code search tool. It does not explicitly distinguish itself from sibling search tools like search_wiki or search_work_items, but the resource 'code' makes the distinction inferable.

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?

Provides no guidance on when to use this tool versus alternatives such as search_wiki or search_work_items, nor any prerequisites or exclusions. Usage is only implied by the word 'Search'.

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