Skip to main content
Glama
stefanskiasan

Azure DevOps MCP Server for Cline

list_work_items

Retrieve work items from Azure DevOps boards using WIQL queries to filter and organize tasks, bugs, and features for project tracking.

Instructions

List work items from a board

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesWIQL query to filter work items

Implementation Reference

  • The core handler function that executes a WIQL query against the Azure DevOps Work Item Tracking API and formats the result as MCP content.
    export async function listWorkItems(args: Wiql, config: AzureDevOpsConfig) {
      if (!args.query) {
        throw new McpError(ErrorCode.InvalidParams, 'Invalid WIQL query');
      }
    
      AzureDevOpsConnection.initialize(config);
      const connection = AzureDevOpsConnection.getInstance();
      const workItemTrackingApi = await connection.getWorkItemTrackingApi();
      
      const queryResult = await workItemTrackingApi.queryByWiql(
        args,
        { project: config.project }
      );
    
      return {
        content: [
          {
            type: 'text',
            text: JSON.stringify(queryResult, null, 2),
          },
        ],
      };
    }
  • Input schema for the list_work_items tool, requiring a 'query' string parameter for the WIQL query.
    inputSchema: {
      type: 'object',
      properties: {
        query: {
          type: 'string',
          description: 'WIQL query to filter work items',
        },
      },
      required: ['query'],
    },
  • Registration of the list_work_items tool in the definitions array, including name, description, and schema.
    {
      name: 'list_work_items',
      description: 'List work items from a board',
      inputSchema: {
        type: 'object',
        properties: {
          query: {
            type: 'string',
            description: 'WIQL query to filter work items',
          },
        },
        required: ['query'],
      },
    },
  • src/index.ts:129-131 (registration)
    Main server dispatch case that calls the listWorkItems tool handler upon invocation.
    case 'list_work_items':
      result = await tools.workItem.listWorkItems(request.params.arguments);
      break;
  • Wrapper registration that binds the listWorkItems handler to the tool instance with config.
    listWorkItems: (args: Wiql) => listWorkItems(args, config),
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 states the action ('list') but doesn't describe what 'list' entails—e.g., whether it returns all items, supports pagination, requires authentication, or has rate limits. For a tool with no annotation coverage, this leaves critical behavioral traits unspecified, though it doesn't contradict any annotations.

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, efficient sentence with zero wasted words—'List work items from a board' directly conveys the tool's function. It's appropriately front-loaded with the core action and resource, making it easy to parse. No extraneous details or redundancy are present, earning full marks for conciseness.

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?

Given the tool's complexity (a list operation with filtering), lack of annotations, and no output schema, the description is incomplete. It doesn't address return format (e.g., list structure, fields included), pagination, error conditions, or authentication needs. For a tool that likely interacts with a board system, this leaves significant gaps in understanding how to use it effectively.

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 input schema has 100% description coverage, with the single parameter 'query' documented as 'WIQL query to filter work items'. The description adds no additional parameter semantics beyond this, as it doesn't explain WIQL syntax, provide examples, or clarify filtering scope. Given the high schema coverage, a baseline score of 3 is appropriate, as the schema does the heavy lifting.

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 clearly states the verb 'list' and resource 'work items from a board', making the purpose immediately understandable. It distinguishes this from sibling tools like 'get_work_item' (singular retrieval) and 'create_work_item' (creation), though it doesn't explicitly mention these distinctions. The description is specific enough to understand the core function without being tautological.

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. It doesn't mention when to use 'list_work_items' versus 'get_work_item' (for single items) or 'get_boards' (for board metadata), nor does it specify prerequisites like needing board access. The agent must infer usage from context alone, which is insufficient for clear decision-making.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/stefanskiasan/azure-devops-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server