Skip to main content
Glama
javerthl

ServiceNow MCP Server

by javerthl

get_script_include

Retrieve a specific script include from ServiceNow using its ID or name to access server-side logic and functionality.

Instructions

Get a specific script include from ServiceNow

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
script_include_idYesScript include ID or name

Implementation Reference

  • Main handler function that fetches the Script Include record from ServiceNow API using sys_id or name, parses the response, and returns structured data.
    def get_script_include(
        config: ServerConfig,
        auth_manager: AuthManager,
        params: GetScriptIncludeParams,
    ) -> Dict[str, Any]:
        """Get a specific script include from ServiceNow.
        
        Args:
            config: The server configuration.
            auth_manager: The authentication manager.
            params: The parameters for the request.
            
        Returns:
            A dictionary containing the script include data.
        """
        try:
            # Build query parameters
            query_params = {
                "sysparm_display_value": "true",
                "sysparm_exclude_reference_link": "true",
                "sysparm_fields": "sys_id,name,script,description,api_name,client_callable,active,access,sys_created_on,sys_updated_on,sys_created_by,sys_updated_by"
            }
            
            # Determine if we're querying by sys_id or name
            if params.script_include_id.startswith("sys_id:"):
                sys_id = params.script_include_id.replace("sys_id:", "")
                url = f"{config.instance_url}/api/now/table/sys_script_include/{sys_id}"
            else:
                # Query by name
                url = f"{config.instance_url}/api/now/table/sys_script_include"
                query_params["sysparm_query"] = f"name={params.script_include_id}"
                
            # Make the request
            headers = auth_manager.get_headers()
            
            response = requests.get(
                url,
                params=query_params,
                headers=headers,
                timeout=30,
            )
            response.raise_for_status()
            
            # Parse the response
            data = response.json()
            
            if "result" not in data:
                return {
                    "success": False,
                    "message": f"Script include not found: {params.script_include_id}",
                }
                
            # Handle both single result and list of results
            result = data["result"]
            if isinstance(result, list):
                if not result:
                    return {
                        "success": False,
                        "message": f"Script include not found: {params.script_include_id}",
                    }
                item = result[0]
            else:
                item = result
                
            script_include = {
                "sys_id": item.get("sys_id"),
                "name": item.get("name"),
                "script": item.get("script"),
                "description": item.get("description"),
                "api_name": item.get("api_name"),
                "client_callable": item.get("client_callable") == "true",
                "active": item.get("active") == "true",
                "access": item.get("access"),
                "created_on": item.get("sys_created_on"),
                "updated_on": item.get("sys_updated_on"),
                "created_by": item.get("sys_created_by", {}).get("display_value"),
                "updated_by": item.get("sys_updated_by", {}).get("display_value"),
            }
            
            return {
                "success": True,
                "message": f"Found script include: {item.get('name')}",
                "script_include": script_include,
            }
            
        except Exception as e:
            logger.error(f"Error getting script include: {e}")
            return {
                "success": False,
                "message": f"Error getting script include: {str(e)}",
            }
  • Pydantic model defining the input parameters for the get_script_include tool.
    class GetScriptIncludeParams(BaseModel):
        """Parameters for getting a script include."""
        
        script_include_id: str = Field(..., description="Script include ID or name")
  • MCP tool registration entry, specifying the handler function, input schema, return type hint, description, and serialization method.
    "get_script_include": (
        get_script_include_tool,
        GetScriptIncludeParams,
        Dict[str, Any],  # Expects dict
        "Get a specific script include from ServiceNow",
        "raw_dict",  # Tool returns raw dict
    ),
  • Imports the get_script_include function to expose it from the tools module.
    from servicenow_mcp.tools.script_include_tools import (
        create_script_include,
        delete_script_include,
        get_script_include,
        list_script_includes,
        update_script_include,
    )
  • Imports the handler function with alias for use in tool registration.
        get_script_include as get_script_include_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. While 'Get' implies a read operation, the description doesn't specify what information is returned, whether authentication is required, if there are rate limits, or what happens when the script include doesn't exist. This leaves significant gaps for an agent to understand the tool's behavior.

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 communicates the core purpose without any wasted words. It's appropriately sized for a simple retrieval tool and gets straight to the point.

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 simple retrieval tool with one well-documented parameter and no output schema, the description is minimally adequate. However, the lack of annotations means the description should do more to explain behavioral aspects like authentication requirements, error conditions, and return format to be truly complete.

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 the single parameter 'script_include_id' clearly documented as accepting either ID or name. The description adds no additional parameter information beyond what's already in the schema, so the baseline score of 3 is appropriate.

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 ('Get') and resource ('a specific script include from ServiceNow'), making the purpose immediately understandable. However, it doesn't distinguish this tool from its sibling 'list_script_includes' which presumably lists multiple script includes rather than retrieving a specific one.

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 tool is appropriate versus 'list_script_includes', or any context about what constitutes a 'specific script include' that would help an agent choose correctly.

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