Skip to main content
Glama
Vortiago
by Vortiago

get_project_process_id

Retrieve the process ID for an Azure DevOps project to identify its workflow template and enable process-related operations.

Instructions

    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
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
projectYes

Implementation Reference

  • The handler function for the 'get_project_process_id' tool, decorated with @mcp.tool(), which wraps the core implementation and handles exceptions.
    @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)}"
  • Core helper function implementing the logic to retrieve the process ID and details for a given project using the Azure DevOps core client.
    def _get_project_process_id_impl(project: str) -> str:
        """Implementation of project process ID retrieval."""
        try:
            # Get project details with process information
            core_client = get_core_client()
            project_details = core_client.get_project(
                project, include_capabilities=True)
            process_template = project_details.capabilities.get(
                "processTemplate", {})
            
            process_id = process_template.get("templateTypeId")
            process_name = process_template.get("templateName")
            
            if not process_id:
                return f"Could not determine process ID for project {project}."
            
            result = [f"# Process for Project: {project_details.name}"]
            result.append(f"Process Name: {process_name}")
            result.append(f"Process ID: {process_id}")
            
            return "\n".join(result)
        except Exception as e:
            return (f"Error retrieving process ID for project '{project}': "
                    f"{str(e)}")
  • Registration call for the process tools module, which includes get_project_process_id, invoked from the work_items tools init file.
    process.register_tools(mcp)
Behavior3/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 this is a 'get' operation (implying read-only), and mentions the return format includes 'name and ID', which adds useful context. However, it doesn't address potential error conditions, authentication requirements, or rate limits that would be helpful for a tool with no annotation coverage.

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 clear sections: purpose statement, usage guidelines bullet points, Args, and Returns. Every sentence earns its place by providing specific guidance or information without redundancy. The formatting makes it easy to scan and understand.

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?

For a single-parameter tool with no annotations and no output schema, the description does a good job covering purpose, usage, parameters, and return format. The main gap is the lack of error handling or edge case information, but given the tool's apparent simplicity, the description provides sufficient context for effective use.

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 has 0% description coverage, so the description must compensate. It provides the Args section explaining that 'project' accepts 'Project ID or project name', which adds meaningful semantics beyond the bare schema. However, it doesn't provide examples or format specifications for the project parameter.

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' and the resource 'process ID associated with a project', making the purpose specific and unambiguous. It distinguishes this tool from siblings like 'get_process_details' or 'list_processes' by focusing specifically on the project-process relationship.

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 provides explicit bullet points for when to use this tool: 'Find out which process a project is using', 'Get the process ID for use in other process-related operations', and 'Verify process information for a project'. This gives clear context and distinguishes it from alternatives like 'get_process_details' which might provide broader process information.

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