Skip to main content
Glama
JLKmach

ServiceNow MCP Server

by JLKmach

create_story

Create new stories in ServiceNow for agile project management by defining requirements, acceptance criteria, assignments, and tracking details.

Instructions

Create a new story in ServiceNow

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
short_descriptionYesShort description of the story
acceptance_criteriaYesAcceptance criteria for the story
descriptionNoDetailed description of the story
stateNoState of story (-6 is Draft,-7 is Ready for Testing,-8 is Testing,1 is Ready, 2 is Work in progress, 3 is Complete, 4 is Cancelled)
assignment_groupNoGroup assigned to the story
story_pointsNoPoints value for the story
assigned_toNoUser assigned to the story
epicNoEpic that the story belongs to. It requires the System ID of the epic.
projectNoProject that the story belongs to. It requires the System ID of the project.
work_notesNoWork notes to add to the story. Used for adding notes and comments to a story

Implementation Reference

  • The main handler function that implements the create_story tool. It validates input parameters using CreateStoryParams, prepares the data, and makes a POST request to the ServiceNow rm_story table API to create the story.
    def create_story(
        auth_manager: AuthManager,
        server_config: ServerConfig,
        params: Dict[str, Any],
    ) -> Dict[str, Any]:
        """
        Create a new story in ServiceNow.
    
        Args:
            auth_manager: The authentication manager.
            server_config: The server configuration.
            params: The parameters for creating the story.
    
        Returns:
            The created story.
        """
    
        # Unwrap and validate parameters
        result = _unwrap_and_validate_params(
            params, 
            CreateStoryParams, 
            required_fields=["short_description", "acceptance_criteria"]
        )
        
        if not result["success"]:
            return result
        
        validated_params = result["params"]
        
        # Prepare the request data
        data = {
            "short_description": validated_params.short_description,
            "acceptance_criteria": validated_params.acceptance_criteria,
        }
           
        # Add optional fields if provided
        if validated_params.description:
            data["description"] = validated_params.description
        if validated_params.state:
            data["state"] = validated_params.state
        if validated_params.assignment_group:
            data["assignment_group"] = validated_params.assignment_group
        if validated_params.story_points:
            data["story_points"] = validated_params.story_points
        if validated_params.assigned_to:
            data["assigned_to"] = validated_params.assigned_to
        if validated_params.epic:
            data["epic"] = validated_params.epic
        if validated_params.project:
            data["project"] = validated_params.project
        if validated_params.work_notes:
            data["work_notes"] = validated_params.work_notes
        
        # 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/rm_story"
        
        try:
            response = requests.post(url, json=data, headers=headers)
            response.raise_for_status()
            
            result = response.json()
            
            return {
                "success": True,
                "message": "Story created successfully",
                "story": result["result"],
            }
        except requests.exceptions.RequestException as e:
            logger.error(f"Error creating story: {e}")
            return {
                "success": False,
                "message": f"Error creating story: {str(e)}",
            }
  • Pydantic BaseModel defining the input schema/parameters for the create_story tool, including required fields like short_description and acceptance_criteria, and optional fields like state, assignment_group, etc.
    class CreateStoryParams(BaseModel):
        """Parameters for creating a story."""
    
        short_description: str = Field(..., description="Short description of the story")
        acceptance_criteria: str = Field(..., description="Acceptance criteria for the story")
        description: Optional[str] = Field(None, description="Detailed description of the story")
        state: Optional[str] = Field(None, description="State of story (-6 is Draft,-7 is Ready for Testing,-8 is Testing,1 is Ready, 2 is Work in progress, 3 is Complete, 4 is Cancelled)")
        assignment_group: Optional[str] = Field(None, description="Group assigned to the story")
        story_points: Optional[int] = Field(10, description="Points value for the story")
        assigned_to: Optional[str] = Field(None, description="User assigned to the story")
        epic: Optional[str] = Field(None, description="Epic that the story belongs to. It requires the System ID of the epic.")
        project: Optional[str] = Field(None, description="Project that the story belongs to. It requires the System ID of the project.")
        work_notes: Optional[str] = Field(None, description="Work notes to add to the story. Used for adding notes and comments to a story")
  • Registration of the 'create_story' tool in the central tool_definitions dictionary, mapping the tool name to its handler (create_story_tool), input schema (CreateStoryParams), return type, description, and serialization method.
    "create_story": (
        create_story_tool,
        CreateStoryParams,
        str,
        "Create a new story in ServiceNow",
        "str",
    ),
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/mutation operation, the description doesn't mention required permissions, whether the operation is idempotent, what happens on failure, or what the response contains. For a creation tool with 10 parameters and no output schema, this leaves significant behavioral questions unanswered.

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 gets straight to the point with zero wasted words. It's appropriately sized for a tool with a clear purpose and doesn't bury important information in unnecessary verbiage.

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 the complexity (10 parameters, no annotations, no output schema) and the fact this is a creation/mutation tool, the description is insufficient. It doesn't explain what a 'story' is in ServiceNow context, doesn't provide usage guidance among similar creation tools, and offers no behavioral context about permissions, side effects, or return values. For a tool that creates a business entity with many configurable fields, more 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?

The schema description coverage is 100%, with each parameter well-documented in the schema itself. The description adds no additional parameter information beyond what's already in the schema. According to the scoring rules, when schema_description_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 ('a new story in ServiceNow'), making the purpose immediately understandable. However, it doesn't differentiate this tool from sibling creation tools like 'create_epic', 'create_project', or 'create_change_request', which all follow the same pattern of creating different ServiceNow entities.

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. With many sibling tools that create different ServiceNow entities (epics, projects, change requests, etc.), there's no indication of what constitutes a 'story' versus these other entities or when each should be used. No prerequisites, constraints, or exclusions are mentioned.

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