Skip to main content
Glama
javerthl

ServiceNow MCP Server

by javerthl

update_project

Modify an existing ServiceNow project by updating its details such as status, description, assignment group, completion percentage, and timeline information.

Instructions

Update an existing project in ServiceNow

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
assigned_toNoUser assigned to the project
assignment_groupNoGroup assigned to the project
descriptionNoDetailed description of the project
end_dateNoEnd date for the project
percentage_completeNoPercentage complete for the project
project_idYesProject ID or sys_id
project_managerNoProject manager for the project
short_descriptionNoProject name of the project
start_dateNoStart date for the project
stateNoState of project (-5 is Pending,1 is Open, 2 is Work in progress, 3 is Closed Complete, 4 is Closed Incomplete, 5 is Closed Skipped)
statusNoStatus of the project (green, yellow, red)

Implementation Reference

  • The core handler function implementing the update_project tool. It validates input parameters using UpdateProjectParams, prepares a PUT request to the ServiceNow pm_project table API, handles authentication via config and auth_manager, and returns success/error responses with project details.
    def update_project(
        config: ServerConfig,  # Changed from auth_manager
        auth_manager: AuthManager,  # Changed from server_config
        params: Dict[str, Any],
    ) -> Dict[str, Any]:
        """
        Update an existing project in ServiceNow.
    
        Args:
            config: The server configuration.
            auth_manager: The authentication manager.
            params: The parameters for updating the project.
    
        Returns:
            The updated project.
        """
        # Unwrap and validate parameters
        result = _unwrap_and_validate_params(
            params, 
            UpdateProjectParams,
            required_fields=["project_id"]
        )
        
        if not result["success"]:
            return result
        
        validated_params = result["params"]
        
        # Prepare the request data
        data = {}
    
        # Add optional fields if provided
        if validated_params.short_description:
            data["short_description"] = validated_params.short_description
        if validated_params.description:
            data["description"] = validated_params.description
        if validated_params.status:
            data["status"] = validated_params.status
        if validated_params.state:
            data["state"] = validated_params.state
        if validated_params.assignment_group:
            data["assignment_group"] = validated_params.assignment_group
        if validated_params.percentage_complete:
            data["percentage_complete"] = validated_params.percentage_complete
        if validated_params.assigned_to:
            data["assigned_to"] = validated_params.assigned_to
        if validated_params.project_manager:
            data["project_manager"] = validated_params.project_manager
        if validated_params.start_date:
            data["start_date"] = validated_params.start_date
        if validated_params.end_date:
            data["end_date"] = validated_params.end_date
    
        # Get the instance URL
        instance_url = _get_instance_url(auth_manager, config)
        if not instance_url:
            return {
                "success": False,
                "message": "Cannot find instance_url in either server_config or auth_manager",
            }
        
        # Get the headers
        headers = _get_headers(auth_manager, config)
        if not headers:
            return {
                "success": False,
                "message": "Cannot find get_headers method in either auth_manager or server_config",
            }
        
        # Add Content-Type header
        headers["Content-Type"] = "application/json"
        
        # Make the API request
        url = f"{instance_url}/api/now/table/pm_project/{validated_params.project_id}"
        
        try:
            response = requests.put(url, json=data, headers=headers)
            response.raise_for_status()
            
            result = response.json()
            
            return {
                "success": True,
                "message": "Project updated successfully",
                "project": result["result"],
            }
        except requests.exceptions.RequestException as e:
            logger.error(f"Error updating project: {e}")
            return {
                "success": False,
                "message": f"Error updating project: {str(e)}",
            }
  • Pydantic BaseModel defining the input schema for the update_project tool, including required project_id and optional fields for project attributes.
    class UpdateProjectParams(BaseModel):
        """Parameters for updating a project."""
    
        project_id: str = Field(..., description="Project ID or sys_id")
        short_description: Optional[str] = Field(None, description="Project name of the project")
        description: Optional[str] = Field(None, description="Detailed description of the project")
        status: Optional[str] = Field(None, description="Status of the project (green, yellow, red)")
        state: Optional[str] = Field(None, description="State of project (-5 is Pending,1 is Open, 2 is Work in progress, 3 is Closed Complete, 4 is Closed Incomplete, 5 is Closed Skipped)")
        project_manager: Optional[str] = Field(None, description="Project manager for the project")
        percentage_complete: Optional[int] = Field(None, description="Percentage complete for the project")
        assignment_group: Optional[str] = Field(None, description="Group assigned to the project")
        assigned_to: Optional[str] = Field(None, description="User assigned to the project")
        start_date: Optional[str] = Field(None, description="Start date for the project")
        end_date: Optional[str] = Field(None, description="End date for the project")
  • Registration entry in the get_tool_definitions() function's tool_definitions dictionary. Maps the 'update_project' name to its aliased handler function, input schema, return type hint, description, and serialization method ('str'). This centralizes tool registration for the MCP server.
    "update_project": (
        update_project_tool,
        UpdateProjectParams,
        str,
        "Update an existing project in ServiceNow",
        "str",
    ),
  • Import aliasing the update_project function from project_tools.py as update_project_tool, used in the tool definitions dictionary for registration.
    from servicenow_mcp.tools.project_tools import (
        create_project as create_project_tool,
        update_project as update_project_tool,
        list_projects as list_projects_tool,
    )
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 'Update' implies a mutation, but fails to mention critical details like required permissions, whether changes are reversible, error handling, or what the response contains. This is inadequate for a mutation tool with zero 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 a single, efficient sentence that directly states the tool's purpose without any wasted words. It's appropriately sized and front-loaded, making it easy to parse quickly.

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?

For a mutation tool with 11 parameters, no annotations, and no output schema, the description is insufficient. It lacks behavioral context, usage guidelines, and output information, leaving significant gaps for an agent to understand how to use this tool 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?

Schema description coverage is 100%, so the schema fully documents all 11 parameters. The description adds no additional parameter information beyond what's in the schema, meeting the baseline score of 3 where 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 ('Update') and resource ('an existing project in ServiceNow'), making the purpose unambiguous. However, it doesn't differentiate from sibling tools like 'update_change_request' or 'update_incident' beyond the resource type, which is why it doesn't reach a perfect score.

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 prerequisites (e.g., needing an existing project ID), compare to 'create_project' for new projects, or indicate any contextual constraints, leaving the agent without usage direction.

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/javerthl/servicenow-mcp'

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