Skip to main content
Glama
javerthl

ServiceNow MCP Server

by javerthl

get_workflow_details

Retrieve comprehensive details about a ServiceNow workflow, including its configuration and optional version history, to understand workflow structure and functionality.

Instructions

Get detailed information about a specific workflow

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
include_versionsNoInclude workflow versions
workflow_idYesWorkflow ID or sys_id

Implementation Reference

  • Main handler function implementing the get_workflow_details tool. Fetches workflow details from ServiceNow wf_workflow table using the provided workflow_id.
    def get_workflow_details(
        auth_manager: AuthManager,
        server_config: ServerConfig,
        params: Dict[str, Any],
    ) -> Dict[str, Any]:
        """
        Get detailed information about a specific workflow.
        
        Args:
            auth_manager: Authentication manager
            server_config: Server configuration
            params: Parameters for getting workflow details
            
        Returns:
            Dictionary containing the workflow details
        """
        params = _unwrap_params(params, GetWorkflowDetailsParams)
        
        # Get the correct auth_manager and server_config
        try:
            auth_manager, server_config = _get_auth_and_config(auth_manager, server_config)
        except ValueError as e:
            logger.error(f"Error getting auth and config: {e}")
            return {"error": str(e)}
        
        workflow_id = params.get("workflow_id")
        if not workflow_id:
            return {"error": "Workflow ID is required"}
        
        # Make the API request
        try:
            headers = auth_manager.get_headers()
            url = f"{server_config.instance_url}/api/now/table/wf_workflow/{workflow_id}"
            
            response = requests.get(url, headers=headers)
            response.raise_for_status()
            
            result = response.json()
            return {
                "workflow": result.get("result", {}),
            }
        except requests.RequestException as e:
            logger.error(f"Error getting workflow details: {e}")
            return {"error": str(e)}
        except Exception as e:
            logger.error(f"Unexpected error getting workflow details: {e}")
            return {"error": str(e)}
  • Pydantic schema defining input parameters for the get_workflow_details tool.
    class GetWorkflowDetailsParams(BaseModel):
        """Parameters for getting workflow details."""
        
        workflow_id: str = Field(..., description="Workflow ID or sys_id")
        include_versions: Optional[bool] = Field(False, description="Include workflow versions")
  • Tool registration entry in the central get_tool_definitions dictionary, mapping name to implementation, schema, return type hint, description, and serialization method.
    "get_workflow_details": (
        get_workflow_details_tool,
        GetWorkflowDetailsParams,
        str,  # Expects JSON string
        "Get detailed information about a specific workflow",
        "json",  # Tool returns list/dict
    ),
  • Helper utility used by workflow tools to normalize auth_manager and server_config arguments, supporting flexible parameter order.
    def _get_auth_and_config(
        auth_manager_or_config: Union[AuthManager, ServerConfig],
        server_config_or_auth: Union[ServerConfig, AuthManager],
    ) -> tuple[AuthManager, ServerConfig]:
        """
        Get the correct auth_manager and server_config objects.
        
        This function handles the case where the parameters might be swapped.
        
        Args:
            auth_manager_or_config: Either an AuthManager or a ServerConfig.
            server_config_or_auth: Either a ServerConfig or an AuthManager.
            
        Returns:
            tuple[AuthManager, ServerConfig]: The correct auth_manager and server_config.
            
        Raises:
            ValueError: If the parameters are not of the expected types.
        """
        # Check if the parameters are in the correct order
        if isinstance(auth_manager_or_config, AuthManager) and isinstance(server_config_or_auth, ServerConfig):
            return auth_manager_or_config, server_config_or_auth
        
        # Check if the parameters are swapped
        if isinstance(auth_manager_or_config, ServerConfig) and isinstance(server_config_or_auth, AuthManager):
            return server_config_or_auth, auth_manager_or_config
        
        # If we get here, at least one of the parameters is not of the expected type
        if hasattr(auth_manager_or_config, "get_headers"):
            auth_manager = auth_manager_or_config
        elif hasattr(server_config_or_auth, "get_headers"):
            auth_manager = server_config_or_auth
        else:
            raise ValueError("Cannot find get_headers method in either auth_manager or server_config")
        
        if hasattr(auth_manager_or_config, "instance_url"):
            server_config = auth_manager_or_config
        elif hasattr(server_config_or_auth, "instance_url"):
            server_config = server_config_or_auth
        else:
            raise ValueError("Cannot find instance_url attribute in either auth_manager or server_config")
        
        return auth_manager, server_config
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. While 'Get detailed information' implies a read operation, it doesn't specify what constitutes 'detailed information', whether authentication is required, rate limits, error conditions, or response format. The description is too vague for a tool with no annotation support.

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 that gets straight to the point. There's no wasted language or unnecessary elaboration. However, it could be more front-loaded with critical context given the lack of annotations.

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?

For a read operation tool with no annotations and no output schema, the description is insufficient. It doesn't explain what 'detailed information' includes, the response format, error handling, or authentication requirements. Given the complexity implied by sibling tools and the lack of structured support, more descriptive context is needed.

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 fully documents both parameters. The description doesn't add any parameter semantics beyond what's in the schema - it doesn't explain what 'detailed information' includes or how the 'include_versions' parameter affects the output. 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 states 'Get detailed information about a specific workflow' which clearly indicates a read operation on a workflow resource. However, it doesn't differentiate from sibling tools like 'get_workflow_activities' or 'list_workflows' which also retrieve workflow-related information. The purpose is clear but lacks sibling differentiation.

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 when to use 'get_workflow_details' versus 'list_workflows' or 'get_workflow_activities', nor any prerequisites or constraints. The agent must infer usage from the 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