Skip to main content
Glama

advance_hr_case

Move an HR case to its next state or a specified target state, optionally adding a work note. Use it to progress ServiceNow HRSD cases through their lifecycle stages.

Instructions

Advance an HR case to its next state/stage (sn_hr_core_case). Parity with ServiceNow HRSD "HR Case Advance". Requires WRITE_ENABLED=true

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "case": "<case>"
    },
    "name": "advance_hr_case"
  }
}

Input Schema

NameRequiredDescriptionDefault
caseYesHR case number or sys_id
stateNoTarget state value (if known); otherwise increments the current state
work_notesNoOptional work note to add on advance

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv4.15.1

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare non-read-only, non-idempotent, non-destructive. The description adds genuine context beyond them: the WRITE_ENABLED=true configuration gate and the fact that omitting a state will self-increment the case forward, which explains the non-idempotent hint in practical terms. It still omits side effects such as approvals, notifications, or what happens on the final stage.

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?

Three compact sentences with the action front-loaded and the prerequisite in a clearly separable clause. The ServiceNow parity note is mildly redundant but does convey platform semantics cheaply.

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 non-idempotent mutation with no output schema, the definition covers the core action and config prerequisite, but leaves open the return value, failure modes (e.g., no next state available), and whether advancing triggers approvals or notifications. Adequate but not complete for the tool's complexity.

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 all three parameters are already documented, including the 'otherwise increments the current state' fallback for state. The description adds no syntax, allowed value, or constraint detail beyond the schema, so the baseline 3 applies.

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?

States a specific verb and resource (advance an HR case) and the underlying object (sn_hr_core_case), plus the direction of movement (next state/stage). It does not explicitly distinguish itself from close_hr_case or update_hr_case, which also mutate HR case state, so sibling differentiation is left to inference.

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

Usage Guidelines3/5

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

The usage context is implied by the state-machine framing, and it names a concrete prerequisite (WRITE_ENABLED=true). However, it never says when to prefer this over update_hr_case or close_hr_case, nor what to do if the case is already at a terminal state.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools