Skip to main content
Glama
echelon-ai-labs

ServiceNow MCP Server

delete_script_include

Remove a script include from a ServiceNow instance by specifying its ID or name. This tool facilitates efficient script management via the ServiceNow API.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
paramsYes

Implementation Reference

  • The handler function that implements the core logic for the 'delete_script_include' tool. It retrieves the script include by ID, constructs the API URL, and sends a DELETE request to the ServiceNow REST API.
    def delete_script_include(
        config: ServerConfig,
        auth_manager: AuthManager,
        params: DeleteScriptIncludeParams,
    ) -> ScriptIncludeResponse:
        """Delete a script include from ServiceNow.
        
        Args:
            config: The server configuration.
            auth_manager: The authentication manager.
            params: The parameters for the request.
            
        Returns:
            A response indicating the result of the operation.
        """
        # First, get the script include to delete
        get_params = GetScriptIncludeParams(script_include_id=params.script_include_id)
        get_result = get_script_include(config, auth_manager, get_params)
        
        if not get_result["success"]:
            return ScriptIncludeResponse(
                success=False,
                message=get_result["message"],
            )
            
        script_include = get_result["script_include"]
        sys_id = script_include["sys_id"]
        name = script_include["name"]
        
        # Build the URL
        url = f"{config.instance_url}/api/now/table/sys_script_include/{sys_id}"
        
        # Make the request
        headers = auth_manager.get_headers()
        
        try:
            response = requests.delete(
                url,
                headers=headers,
                timeout=30,
            )
            response.raise_for_status()
            
            return ScriptIncludeResponse(
                success=True,
                message=f"Deleted script include: {name}",
                script_include_id=sys_id,
                script_include_name=name,
            )
            
        except Exception as e:
            logger.error(f"Error deleting script include: {e}")
            return ScriptIncludeResponse(
                success=False,
                message=f"Error deleting script include: {str(e)}",
            ) 
  • Pydantic model defining the input parameters for the delete_script_include tool, requiring a script_include_id.
    class DeleteScriptIncludeParams(BaseModel):
        """Parameters for deleting a script include."""
        
        script_include_id: str = Field(..., description="Script include ID or name")
  • The registration entry for the 'delete_script_include' tool in the central tool definitions dictionary used by the MCP server.
    "delete_script_include": (
        delete_script_include_tool,
        DeleteScriptIncludeParams,
        str,  # Expects JSON string
        "Delete a script include in ServiceNow",
        "json_dict",  # Tool returns Pydantic model
    ),
Behavior1/5

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

Tool has no description.

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

Conciseness1/5

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

Tool has no description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

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

Purpose1/5

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

Tool has no description.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Tool has no description.

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

Related 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/echelon-ai-labs/servicenow-mcp'

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