Skip to main content
Glama
javerthl

ServiceNow MCP Server

by javerthl

create_script_include

Create a new script include in ServiceNow by providing a name, script content, and optional configuration settings for client callable status, access level, and activation.

Instructions

Create a new script include in ServiceNow

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
accessNoAccess level of the script includepackage_private
activeNoWhether the script include is active
api_nameNoAPI name of the script include
client_callableNoWhether the script include is client callable
descriptionNoDescription of the script include
nameYesName of the script include
scriptYesScript content

Implementation Reference

  • The handler function that executes the tool logic: sends a POST request to ServiceNow's sys_script_include table API with the provided parameters to create a new script include.
    def create_script_include(
        config: ServerConfig,
        auth_manager: AuthManager,
        params: CreateScriptIncludeParams,
    ) -> ScriptIncludeResponse:
        """Create a new script include in 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.
        """
        # Build the URL
        url = f"{config.instance_url}/api/now/table/sys_script_include"
        
        # Build the request body
        body = {
            "name": params.name,
            "script": params.script,
            "active": str(params.active).lower(),
            "client_callable": str(params.client_callable).lower(),
            "access": params.access,
        }
        
        if params.description:
            body["description"] = params.description
            
        if params.api_name:
            body["api_name"] = params.api_name
            
        # Make the request
        headers = auth_manager.get_headers()
        
        try:
            response = requests.post(
                url,
                json=body,
                headers=headers,
                timeout=30,
            )
            response.raise_for_status()
            
            # Parse the response
            data = response.json()
            
            if "result" not in data:
                return ScriptIncludeResponse(
                    success=False,
                    message="Failed to create script include",
                )
                
            result = data["result"]
            
            return ScriptIncludeResponse(
                success=True,
                message=f"Created script include: {result.get('name')}",
                script_include_id=result.get("sys_id"),
                script_include_name=result.get("name"),
            )
            
        except Exception as e:
            logger.error(f"Error creating script include: {e}")
            return ScriptIncludeResponse(
                success=False,
                message=f"Error creating script include: {str(e)}",
            )
  • Input schema using Pydantic BaseModel for validating tool parameters.
    class CreateScriptIncludeParams(BaseModel):
        """Parameters for creating a script include."""
        
        name: str = Field(..., description="Name of the script include")
        script: str = Field(..., description="Script content")
        description: Optional[str] = Field(None, description="Description of the script include")
        api_name: Optional[str] = Field(None, description="API name of the script include")
        client_callable: bool = Field(False, description="Whether the script include is client callable")
        active: bool = Field(True, description="Whether the script include is active")
        access: str = Field("package_private", description="Access level of the script include")
  • Tool registration in the get_tool_definitions() function, associating the tool name with its handler (aliased), input schema, return type, description, and serialization method.
    "create_script_include": (
        create_script_include_tool,
        CreateScriptIncludeParams,
        ScriptIncludeResponse,  # Expects Pydantic model
        "Create a new script include in ServiceNow",
        "raw_pydantic",  # Tool returns Pydantic model
    ),
  • Output schema using Pydantic BaseModel for the tool response.
    class ScriptIncludeResponse(BaseModel):
        """Response from script include operations."""
        
        success: bool = Field(..., description="Whether the operation was successful")
        message: str = Field(..., description="Message describing the result")
        script_include_id: Optional[str] = Field(None, description="ID of the affected script include")
        script_include_name: Optional[str] = Field(None, description="Name of the affected script include")
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. While 'Create' implies a write operation, the description doesn't mention permission requirements, whether this operation is idempotent, what happens on duplicate names, or what the response looks like. For a creation tool with zero annotation coverage, this is a significant gap in behavioral context.

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 states exactly what the tool does without any wasted words. It's appropriately sized and front-loaded with the essential information.

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

Completeness3/5

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

For a creation tool with 7 parameters (2 required), no annotations, and no output schema, the description is minimally adequate. It states what the tool does but doesn't provide behavioral context, usage guidance, or information about the return value. The high schema coverage helps, but the description alone doesn't provide complete context for proper tool invocation.

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 schema description coverage is 100%, so the schema already documents all 7 parameters thoroughly. The description adds no parameter-specific information beyond what's in the schema. According to scoring rules, when schema coverage is high (>80%), the baseline 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 script include in ServiceNow'), providing a specific verb+resource combination. However, it doesn't differentiate this from sibling tools like 'update_script_include' or 'delete_script_include' beyond the obvious creation vs modification/deletion distinction.

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. There's no mention of prerequisites, when this operation is appropriate, or what distinguishes it from similar tools like 'update_script_include' or 'get_script_include' beyond the basic create/read/update distinction.

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