Skip to main content
Glama

BRAINIAC HR Operations

List offboarding tasks

hr-operations_employee-offboarding-checklist

Build an offboarding checklist only from supplied offboarding policies. A task is met only by a supplied completion record. Access is not changed. Price $0.05 USDC. POST /api/v1/hr-operations/employee-offboarding-checklist. Unpaid calls return 402 and do not run.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "hr-operations_employee-offboarding-checklist"
  }
}

Input Schema

NameRequiredDescriptionDefault
csvNo
asOfNo
fileNo
jsonNo
textNo
policiesNo
roleTextNo
documentsNo
employeesNo
withinDaysNo
completionsNo
employeeTextNo
requirementsNo
acknowledgementsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3/5.0
Behavior4/5

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

With no annotations, the description does real work: it declares no side effects on access ('Access is not changed'), the evaluation rule for task satisfaction (only a supplied completion record counts), and payment behavior including the $0.05 USDC cost and 402 on unpaid calls. It still omits what happens when required inputs like employees or completions are missing.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is short and front-loads the core purpose, but the remaining sentences are a disjointed stack of facts — matching rule, side-effect note, price, endpoint, and payment failure — with no grouping or connective structure. Nothing is padded, but the telegraphic style makes the operational details feel bolted on.

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 14-parameter tool with nested objects, zero schema descriptions, no annotations, and no output schema, the description is far too thin. It never explains the alternative input representations or how the checklist is scoped by time or role, which an agent needs to call it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across 14 parameters, so the description must compensate and largely does not. It hints at the 'policies' and 'completions' inputs but says nothing about the csv/json/text/file input modes, asOf, withinDays, requirements, roleText, or employeeText, leaving most of the surface undocumented anywhere.

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 ('Build an offboarding checklist') and scopes it to supplied offboarding policies. The offboarding framing distinguishes it from the sibling onboarding-checklist tool, though no sibling is named explicitly.

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 when-to-use or when-not-to-use guidance relative to alternatives such as record-completeness-report or policy-acknowledgement-check. The only constraint given is an input precondition ('only from supplied offboarding policies'), which is a data requirement rather than invocation guidance.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources