Skip to main content
Glama
Vortiago
by Vortiago

list_processes

Lists available processes in Azure DevOps to identify process IDs for project creation and check default configurations.

Instructions

    Lists all available processes in the organization.
    
    Use this tool when you need to:
    - See what processes are available in your Azure DevOps organization
    - Find process IDs for project creation or configuration
    - Check which process is set as the default
    
    Returns:
        A formatted table of all processes with names, IDs, and 
        descriptions
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The MCP tool handler function for 'list_processes', decorated with @mcp.tool(). It wraps the core implementation and handles exceptions.
    @mcp.tool()
    def list_processes() -> str:
        """
        Lists all available processes in the organization.
        
        Use this tool when you need to:
        - See what processes are available in your Azure DevOps organization
        - Find process IDs for project creation or configuration
        - Check which process is set as the default
        
        Returns:
            A formatted table of all processes with names, IDs, and 
            descriptions
        """
        try:
            return _list_processes_impl()
        except Exception as e:
            return f"Error: {str(e)}"
  • Core implementation that fetches the list of processes using the Azure DevOps client, formats them into a markdown table, and returns the result.
    def _list_processes_impl() -> str:
        """Implementation of processes list retrieval."""
        try:
            process_client = get_work_item_tracking_process_client()
            processes = process_client.get_list_of_processes()
            
            if not processes:
                return "No processes found in the organization."
            
            result = ["# Available Processes"]
            
            headers = ["Name", "ID", "Reference Name", "Description", "Is Default"]
            rows = []
            for process in processes:
                is_default = ("Yes" if getattr(process.properties, 
                                            'is_default', False) 
                              else "No")
                row = (f"| {process.name} | {process.type_id} | " +
                       f"{getattr(process, 'reference_name', 'N/A')} | " +
                       f"{getattr(process, 'description', 'N/A')} | " +
                       f"{is_default} |")
                rows.append(row)
            
            result.append(_format_table(headers, rows))
            return "\n".join(result)
        except Exception as e:
            return f"Error retrieving processes: {str(e)}"
  • The registration call for process tools within the work_items tools aggregator, which triggers the definition and registration of the list_processes tool.
    process.register_tools(mcp)
  • Utility function used to format the processes list as a markdown table.
    def _format_table(headers, rows):
        """Format data as a markdown table."""
        result = []
        result.append("| " + " | ".join(headers) + " |")
        result.append("| " + " | ".join(["----"] * len(headers)) + " |")
        result.extend(rows)
        return "\n".join(result)
  • The register_tools function that defines and registers all process-related tools, including list_processes, using @mcp.tool() decorators.
    def register_tools(mcp) -> None:
        """
        Register process tools with the MCP server.
        
        Args:
            mcp: The FastMCP server instance
        """
        
        @mcp.tool()
        def get_project_process_id(project: str) -> str:
            """
            Gets the process ID associated with a project.
            
            Use this tool when you need to:
            - Find out which process a project is using
            - Get the process ID for use in other process-related operations
            - Verify process information for a project
            
            Args:
                project: Project ID or project name
                
            Returns:
                Formatted information about the process including name and ID
            """
            try:
                return _get_project_process_id_impl(project)
            except Exception as e:
                return f"Error: {str(e)}"
        
        @mcp.tool()
        def get_process_details(process_id: str) -> str:
            """
            Gets detailed information about a specific process.
            
            Use this tool when you need to:
            - View process properties and configuration
            - Get a list of work item types defined in a process
            - Check if a process is the default for the organization
            
            Args:
                process_id: The ID of the process
                
            Returns:
                Detailed information about the process including properties and
                available work item types
            """
            try:
                return _get_process_details_impl(process_id)
            except Exception as e:
                return f"Error: {str(e)}"
        
        @mcp.tool()
        def list_processes() -> str:
            """
            Lists all available processes in the organization.
            
            Use this tool when you need to:
            - See what processes are available in your Azure DevOps organization
            - Find process IDs for project creation or configuration
            - Check which process is set as the default
            
            Returns:
                A formatted table of all processes with names, IDs, and 
                descriptions
            """
            try:
                return _list_processes_impl()
            except Exception as e:
                return f"Error: {str(e)}"
Behavior4/5

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

No annotations are provided, so the description carries the full burden. It discloses that the tool returns a formatted table with names, IDs, and descriptions, which is useful behavioral context. However, it doesn't mention potential limitations like pagination, rate limits, or authentication requirements, leaving some gaps for a tool with organizational scope.

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 well-structured with a clear purpose statement followed by bulleted usage guidelines and return format. Every sentence adds value without redundancy, and it's front-loaded with the core functionality. The formatting enhances readability without being verbose.

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?

Given 0 parameters, no annotations, and no output schema, the description does a good job explaining what the tool does, when to use it, and what it returns. However, for a tool that lists organizational resources, it could benefit from mentioning potential scope or permission considerations to be fully complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has 0 parameters with 100% coverage, so no parameter documentation is needed. The description appropriately doesn't discuss parameters, focusing instead on usage and output. A baseline of 4 is applied since there are no parameters to document.

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 states the specific verb 'Lists' and resource 'all available processes in the organization.' It distinguishes from siblings like 'get_process_details' (which retrieves details for a specific process) and 'get_project_process_id' (which focuses on a project's process). The purpose is specific and well-differentiated.

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

Usage Guidelines5/5

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

The description explicitly provides three bullet points detailing when to use this tool: to see available processes, find process IDs for project creation/configuration, and check the default process. This gives clear context for usage without needing to mention alternatives, which is appropriate for a list operation.

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/Vortiago/mcp-azure-devops'

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