Skip to main content
Glama
Vortiago
by Vortiago

get_process_details

Retrieve detailed information about Azure DevOps processes, including properties, configuration, work item types, and default status.

Instructions

    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
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
process_idYes

Implementation Reference

  • Core handler logic that retrieves process details using Azure DevOps Work Item Tracking Process Client, including properties and work item types, formatted as Markdown.
    def _get_process_details_impl(process_id: str) -> str:
        """Implementation of process details retrieval."""
        try:
            process_client = get_work_item_tracking_process_client()
            process = process_client.get_process_by_its_id(process_id)
            
            if not process:
                return f"Process with ID '{process_id}' not found."
            
            result = [f"# Process: {process.name}"]
            
            if hasattr(process, "description") and process.description:
                result.append(f"\nDescription: {process.description}")
            
            result.append(
                f"Reference Name: {getattr(process, 'reference_name', 'N/A')}")
            result.append(f"Type ID: {getattr(process, 'type_id', 'N/A')}")
            
            # Get process properties like isDefault, isEnabled, etc.
            properties = getattr(process, "properties", None)
            if properties:
                result.append("\n## Properties")
                for attr in ["is_default", "is_enabled"]:
                    value = getattr(properties, attr, None)
                    if value is not None:
                        attr_name = attr.replace("_", " ").capitalize()
                        result.append(f"{attr_name}: {value}")
            
            # Get work item types for this process
            wit_types = process_client.get_process_work_item_types(process_id)
            if wit_types:
                result.append("\n## Work Item Types")
                
                headers = ["Name", "Reference Name", "Description"]
                rows = [
                    f"| {wit.name} | {getattr(wit, 'reference_name', 'N/A')} | " +
                    f"{getattr(wit, 'description', 'N/A')} |"
                    for wit in wit_types
                ]
                
                result.append(_format_table(headers, rows))
            
            return "\n".join(result)
        except Exception as e:
            return (f"Error retrieving process details for process ID "
                    f"'{process_id}': {str(e)}")
  • MCP tool registration using @mcp.tool() decorator, defining the entry point for 'get_process_details' which delegates to the implementation.
    @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)}"
  • Docstring providing input schema (process_id: str) and output description for the get_process_details tool.
    """
    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
    """
  • Invocation of process.register_tools(mcp) which registers the get_process_details tool among others.
    process.register_tools(mcp)
  • Utility function used to format lists of work item types and other tabular data into Markdown tables.
    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)
Behavior3/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 implies a read-only operation ('Gets detailed information'), which is appropriate, but doesn't disclose behavioral traits like authentication requirements, rate limits, error conditions, or response format details. The description adds value by specifying what information is returned but lacks operational context.

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, bulleted usage guidelines, and separate sections for Args and Returns. Every sentence earns its place by adding specific value without redundancy, and it's front-loaded with the core functionality.

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 the tool's moderate complexity (single parameter, read operation) and lack of annotations or output schema, the description is fairly complete. It covers purpose, usage, parameters, and return information, but could improve by adding more behavioral details like error handling or response structure to fully compensate for missing structured data.

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 schema description coverage is 0%, so the description must compensate. It documents the single parameter 'process_id' with a brief explanation ('The ID of the process'), which adds meaning beyond the schema's title 'Process Id'. However, it doesn't provide format examples or constraints, leaving some ambiguity.

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 verb ('Gets detailed information') and resource ('about a specific process'), distinguishing it from siblings like 'list_processes' (which lists processes) and 'get_work_item' (which focuses on work items). It specifies the scope of details including properties, configuration, work item types, and default status.

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 usage scenarios in a bulleted list: 'View process properties and configuration', 'Get a list of work item types defined in a process', and 'Check if a process is the default for the organization'. This gives clear context for when to use this tool versus alternatives like 'list_processes' or 'get_work_item_types'.

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