Skip to main content
Glama
JLKmach

ServiceNow MCP Server

by JLKmach

submit_change_for_approval

Submit a change request for approval in ServiceNow by providing the change ID and optional comments to initiate the review process.

Instructions

Submit a change request for approval

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
change_idYesChange request ID or sys_id
approval_commentsNoComments for the approval request

Implementation Reference

  • Main handler function implementing the tool logic: validates params, updates change_request state to 'assess', creates approval record in sysapproval_approver table.
    def submit_change_for_approval(
        auth_manager: AuthManager,
        server_config: ServerConfig,
        params: Dict[str, Any],
    ) -> Dict[str, Any]:
        """
        Submit a change request for approval in ServiceNow.
    
        Args:
            auth_manager: The authentication manager.
            server_config: The server configuration.
            params: The parameters for submitting a change request for approval.
    
        Returns:
            The result of the submission.
        """
        # Unwrap and validate parameters
        result = _unwrap_and_validate_params(
            params, 
            SubmitChangeForApprovalParams,
            required_fields=["change_id"]
        )
        
        if not result["success"]:
            return result
        
        validated_params = result["params"]
        
        # Prepare the request data
        data = {
            "state": "assess",  # Set state to "assess" to submit for approval
        }
        
        # Add approval comments if provided
        if validated_params.approval_comments:
            data["work_notes"] = validated_params.approval_comments
        
        # Get the instance URL
        instance_url = _get_instance_url(auth_manager, server_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, server_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/change_request/{validated_params.change_id}"
        
        try:
            response = requests.patch(url, json=data, headers=headers)
            response.raise_for_status()
            
            # Now, create an approval request
            approval_url = f"{instance_url}/api/now/table/sysapproval_approver"
            approval_data = {
                "document_id": validated_params.change_id,
                "source_table": "change_request",
                "state": "requested",
            }
            
            approval_response = requests.post(approval_url, json=approval_data, headers=headers)
            approval_response.raise_for_status()
            
            approval_result = approval_response.json()
            
            return {
                "success": True,
                "message": "Change request submitted for approval successfully",
                "approval": approval_result["result"],
            }
        except requests.exceptions.RequestException as e:
            logger.error(f"Error submitting change for approval: {e}")
            return {
                "success": False,
                "message": f"Error submitting change for approval: {str(e)}",
            }
  • Pydantic schema defining input parameters for the tool.
    class SubmitChangeForApprovalParams(BaseModel):
        """Parameters for submitting a change request for approval."""
    
        change_id: str = Field(..., description="Change request ID or sys_id")
        approval_comments: Optional[str] = Field(None, description="Comments for the approval request")
  • Registration of the tool in the central tool_definitions dictionary used by the MCP server.
    "submit_change_for_approval": (
        submit_change_for_approval_tool,
        SubmitChangeForApprovalParams,
        str,
        "Submit a change request for approval",
        "str",  # Tool returns simple message
    ),
  • Export of the tool function from the tools package __init__.
    submit_change_for_approval,
  • Import alias for the tool handler used in registration.
    from servicenow_mcp.tools.change_tools import (
        submit_change_for_approval as submit_change_for_approval_tool,
    )
Behavior2/5

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

No annotations are provided, so the description carries full burden. It mentions 'submit for approval' but doesn't disclose behavioral traits: whether this is a mutation (likely yes), what permissions are needed, if it triggers notifications, or what happens on success/failure. For a tool with no annotations, this leaves critical gaps in understanding its effects.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, efficient sentence with no wasted words. It's front-loaded with the core action, though it could be more specific. Every word earns its place, but it's borderline under-specified rather than concise.

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 no annotations, no output schema, and a mutation tool (implied by 'submit'), the description is incomplete. It doesn't cover behavioral aspects, return values, error conditions, or how it fits with siblings. For a tool that likely alters system state, more context is needed to guide safe and correct 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?

Schema description coverage is 100%, so the schema already documents both parameters ('change_id' and 'approval_comments') with descriptions. The tool description adds no meaning beyond the schema—it doesn't explain parameter interactions, format examples, or constraints. Baseline 3 is appropriate when schema does the heavy lifting.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Submit a change request for approval' clearly states the verb ('submit') and resource ('change request'), but it's vague about what 'submit' entails—does it initiate approval workflow, send notifications, or update status? It doesn't distinguish from siblings like 'approve_change' or 'reject_change', which are related approval actions.

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?

No guidance on when to use this tool versus alternatives. Sibling tools include 'approve_change' and 'reject_change', but the description doesn't clarify if this is for initiating approval (vs. approving/rejecting) or prerequisites like change request state. It lacks explicit when/when-not instructions or named alternatives.

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

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