Skip to main content
Glama

BRAINIAC HR Operations

List onboarding tasks

hr-operations_employee-onboarding-checklist

Build an onboarding checklist only from supplied onboarding policies. A document or acknowledgement counts only when it matches that policy. No statutory form is added. Price $0.05 USDC. POST /api/v1/hr-operations/employee-onboarding-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-onboarding-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.3/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does disclose meaningful behavior: derivation is limited to supplied policies, documents/acknowledgements only count on a policy match, no statutory forms are injected, and unpaid calls return 402 without executing. What is missing is the return shape and whether results are persisted or idempotent.

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?

Five short sentences with the purpose front-loaded and no filler. The payment and endpoint details are operational metadata rather than task guidance, but they are brief and placed after the substantive rules.

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, nested-object tool with no annotations and no output schema, the description says nothing about how to shape inputs or what a checklist result contains. An agent would have to guess at the relationship between employees, documents, policies and completions, and at the return value.

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, including nested employee, document, policy, completion and requirement objects. The description only obliquely gestures at 'policies', 'document' and 'acknowledgement' inputs and says nothing about csv/json/file/text variants, asOf, withinDays, roleText or employeeText, so it does not compensate for the coverage gap.

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 onboarding checklist') plus a hard scoping rule ('only from supplied onboarding policies'), which lets an agent distinguish it from the offboarding-checklist and policy-acknowledgement siblings. It stops short of explicitly naming an alternative tool, so it is clear but not fully differentiated.

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 description implies the usage context (onboarding checklists derived strictly from the caller's policies) and rules out statutory forms, but it never says when to pick this over the sibling checklist/report tools or what prerequisites must be supplied. Guidance is inferable rather than explicit.

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