Skip to main content
Glama

create_onboarding_case

Creates an employee onboarding case with standard tasks for a new hire using the employee sys_id and start date.

Instructions

Create an employee onboarding case with all standard 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>",
      "start_date": "<start_date>"
    },
    "name": "create_onboarding_case"
  }
}

Input Schema

NameRequiredDescriptionDefault
managerNoManager user sys_id
locationNoOffice location
job_titleNoJob title
departmentNoDepartment name or sys_id
hr_serviceNoHR service sys_id or name (default: the active service whose name contains "onboard")
start_dateYesStart date (ISO 8601)
employee_sys_idYesNew 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 \"onboard\")",
      +  "type": "string"
      +}
  2. First observedv1.0.2

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare this is a non-read-only, non-idempotent, non-destructive, open-world operation. The description adds real behavioral context by stating that all standard tasks are created alongside the case, which the annotations do not convey. It omits permissions requirements and what the response contains, so it is helpful but incomplete.

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 with no filler. The '**[Write]**' tag is redundant with readOnlyHint=false and adds no information an agent does not already have from annotations.

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?

With seven fully documented parameters, a simple create tool, and no output schema, the essentials are covered. However, a mutation tool that silently creates a bundle of tasks should say what is returned (e.g., the case sys_id) and whether the standard task set is fixed or configurable.

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 every parameter including the defaults for hr_service is already documented in the schema. The description adds no parameter meaning beyond that, so the baseline of 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?

The description names a specific verb and resource ('Create an employee onboarding case') and adds the meaningful detail that standard tasks are included. It distinguishes itself from create_offboarding_case by resource context, though it does not explicitly name or contrast with any sibling.

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?

There is no explicit when-to-use or when-not-to-use guidance, and no alternatives are named despite siblings like create_hr_case and create_offboarding_case existing. The only usage signal is the implied 'new hire' context in the word onboarding.

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