arcade-azure-devops-mcp

AzureDevops_SearchIdentities

AzureDevops_SearchIdentities

Search Azure DevOps identities to locate users and groups. Filter by general, account name, display name, or mail address.

Instructions

Search for identities (users/groups) in Azure DevOps.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "search_filter": "<search_filter>",
      "filter_value": "<filter_value>"
    },
    "name": "AzureDevops_SearchIdentities"
  }
}

Input Schema

Name	Required	Description	Default
`filter_value`	Yes	Value to search for
`search_filter`	Yes	Filter type: General, AccountName, DisplayName, MailAddress

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 9, 2026

TDQS

A3.5/5.0

Behavior2/5

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

The description only states that the tool searches, implying a read-only operation, but provides no details about the return format, result limits, authentication needs, or side effects. Since no annotations are present, the description carries the full burden, and this minimal disclosure is insufficient for full transparency.

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, concise sentence without any redundancy. It directly states the tool's purpose and avoids unnecessary words, earning a high score for conciseness and structure.

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

Completeness3/5

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

Given the tool's simplicity and full schema coverage, the description provides a minimal but acceptable overview. However, it lacks context about the output structure or any behavioral limitations, leaving the agent with some uncertainty about what to expect from the call.

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?

The schema description covers both parameters (search_filter and filter_value) with clear descriptions, so the tool description adds no additional semantic value. The schema provides the necessary meaning, giving a baseline score of 3.

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 clearly identifies the action ('Search') and the resource ('identities (users/groups) in Azure DevOps'). It distinguishes itself from sibling tools that target work items, pull requests, and other resources, making the tool's purpose unambiguous.

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

Usage Guidelines3/5

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

The usage is implied: use when searching for identities in Azure DevOps. However, there is no explicit guidance on when to use this tool versus alternatives, nor any exclusions or prerequisites. The implied context from the description is sufficient but not detailed.

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