Skip to main content
Glama
javerthl

ServiceNow MCP Server

by javerthl

create_project

Create a new project in ServiceNow with details like name, description, status, manager, timeline, and assignment information to initiate project tracking and management.

Instructions

Create a new 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_managerNoProject manager for the project
short_descriptionYesProject 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

  • Main handler function that executes the create_project tool: validates params, prepares data, makes POST request to ServiceNow pm_project table, returns result.
    def create_project(
        config: ServerConfig,  # Changed from auth_manager
        auth_manager: AuthManager,  # Changed from server_config
        params: Dict[str, Any],
    ) -> Dict[str, Any]:
        """
        Create a new project in ServiceNow.
    
        Args:
            config: The server configuration.
            auth_manager: The authentication manager.
            params: The parameters for creating the project.
    
        Returns:
            The created project.
        """
    
        # Unwrap and validate parameters
        result = _unwrap_and_validate_params(
            params, 
            CreateProjectParams, 
            required_fields=["short_description"]
        )
        
        if not result["success"]:
            return result
        
        validated_params = result["params"]
        
        # Prepare the request data
        data = {
            "short_description": validated_params.short_description,
        }
    
        # Add optional fields if provided
        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"
        
        try:
            response = requests.post(url, json=data, headers=headers)
            response.raise_for_status()
            
            result = response.json()
            
            return {
                "success": True,
                "message": "Project created successfully",
                "project": result["result"],
            }
        except requests.exceptions.RequestException as e:
            logger.error(f"Error creating project: {e}")
            return {
                "success": False,
                "message": f"Error creating project: {str(e)}",
            }
  • Pydantic BaseModel defining the input schema/parameters for the create_project tool.
    class CreateProjectParams(BaseModel):
        """Parameters for creating a project."""
    
        short_description: str = Field(..., 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")
  • MCP tool registration entry in get_tool_definitions(): maps 'create_project' to handler (create_project_tool), schema (CreateProjectParams), description, and serialization.
    "create_project": (
        create_project_tool,
        CreateProjectParams,
        str,
        "Create a new project in ServiceNow",
        "str",
    ),
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 'Create a new project' which implies a write/mutation operation, but doesn't disclose any behavioral traits such as required permissions, whether the creation is immediate or queued, what happens on failure, or what the response contains (e.g., project ID). For a mutation tool with zero annotation coverage, this leaves significant gaps in understanding how the tool behaves.

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 unnecessary words. It's appropriately sized for a basic creation tool and front-loaded with the essential information. Every word earns its place.

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 complexity (10 parameters, 1 required) and the absence of both annotations and an output schema, the description is insufficiently complete. It doesn't explain what happens after creation (e.g., returns a project ID), what permissions are needed, or how errors are handled. For a mutation tool with many parameters and no structured safety/behavior hints, the description should provide more context to guide proper usage.

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 each parameter clearly documented (e.g., 'User assigned to the project' for assigned_to). The description adds no additional parameter information beyond what the schema provides. According to the rules, when schema_description_coverage is high (>80%), the baseline score is 3 even with no param info in the description.

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 action ('Create') and resource ('new project in ServiceNow'), making the purpose unambiguous. It distinguishes this from sibling tools like 'list_projects' or 'update_project' by specifying creation rather than listing or updating. However, it doesn't explicitly differentiate from other creation tools like 'create_incident' or 'create_change_request' beyond the resource type.

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., required permissions), when not to use it (e.g., for updating existing projects), or how it relates to sibling tools like 'list_projects' or 'update_project'. The agent must infer usage from the tool name alone.

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