Skip to main content
Glama

create_offboarding_case

Creates an employee offboarding case with exit tasks, using employee, last day, reason, manager, and HR service details to start the departure workflow.

Instructions

Create an employee offboarding case with exit tasks. [Write]

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": {
      "employee_sys_id": "<employee_sys_id>",
      "last_day": "<last_day>"
    },
    "name": "create_offboarding_case"
  }
}

Input Schema

NameRequiredDescriptionDefault
reasonNoOffboarding reason (resignation, termination, retirement)
managerNoManager user sys_id
last_dayYesLast working day (ISO 8601)
hr_serviceNoHR service sys_id or name (default: the active service whose name contains "offboard")
employee_sys_idYesDeparting employee user sys_id

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv5.0.1
    • addedInput schema / properties / hr_service
      Added value: +{
      +  "description": "HR service sys_id or name (default: the active service whose name contains \"offboard\")",
      +  "type": "string"
      +}
  2. First observedv1.0.2

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare write (readOnlyHint=false), non-idempotent, non-destructive and open-world, so the safety profile is covered. The description adds one real behavioral fact beyond that: exit tasks are created as a side effect, not just the case record. It says nothing about duplicate-case behavior despite idempotentHint=false, nor about permissions.

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?

One front-loaded sentence plus a write marker, with zero padding. It is terse rather than bloated, though the bracket tag duplicates what annotations already state.

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 five-parameter mutation with no output schema, the definition omits what the caller gets back (e.g., the new case sys_id needed to advance or close it later) and how exit tasks are derived. An agent can invoke it but cannot confidently chain a follow-up call from the description alone.

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 five parameters including the hr_service default resolution are already documented in the schema. The description adds no meaning beyond that, which is the expected baseline when the schema does the heavy lifting.

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 ("Create an employee offboarding case") and adds a distinguishing detail ("with exit tasks") that separates it from a plain HR case. It does not, however, contrast itself with close siblings like create_onboarding_case or create_hr_case, so the agent must infer the boundary.

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?

No guidance on when to choose this over create_hr_case or create_onboarding_case, and no prerequisites stated. The only implied context is 'an employee is leaving', which the agent must derive from the name.

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