Staffology

View saved version →

---
name: task-management
description: Review, create, and update Staffology tasks and assignments for the connected organisation.
---

# Task management

Use Staffology's task tools for task status and explicit task changes in the connected organisation.

- Use `list_tasks` for active tasks, optionally narrowed by priority; use `tasks_today_status` for tasks due today and `unfulfilled_tasks` for incomplete or overdue assignments by employee.
- Use `create_task` only for an explicit creation request. Map the requested name, description, priority, deadline, and assignee exactly. Read those details back before the call; if any detail is inferred or ambiguous, ask for clarification. Call it once and report the returned assignee-match result.
- Use `update_task` only when the target and requested fields are clear. It accepts a partial task name only when exactly one task matches; an ambiguous name is refused and changes nothing.
- Report only changes confirmed by the tool result. A repeated `create_task` call creates another task, and a renamed task cannot safely be retried through its old name.

The task tools cannot edit attendance, approve leave or change pay, and must never stand in for another write. Those operations have their own tools (for example `adjust_attendance_punch` or `approve_leave_request`); use the one that matches the request, or say that none does, and never perform an adjacent task change instead. Nothing on this connector moves money.

View saved version →

---
name: workforce-briefing
description: Summarize Staffology attendance, hours, overtime, task progress, and workforce anomalies for the connected organisation.
---

# Workforce briefing

Use Staffology's live records to answer workforce-status and performance questions for the connected organisation.

- Use `who_is_present` for the live clocked-in, on-break, and clocked-out state.
- Use `employee_activity` for one employee on one day and `employee_monthly` for one employee's calendar month.
- Use `late_arrivals`, `attendance_trends`, or `overtime_summary` for the corresponding measured period. Treat overtime cost as an estimate, not payroll output.
- Use `weekly_digest` for a current-week overview and add `red_flags` only when the user asks for risks or anomalies.
- Use `productivity_ranking` only for requests that explicitly compare task completion. Describe its completion-rate and tasks-per-hour measures without presenting them as work quality.
- Use `daily_report_pdf` or `detailed_report_pdf` only when the user asks for a downloadable report. Each call stores a new file and returns a link valid for two hours.

Choose the narrowest tool that answers the request. Do not infer a location from a punch `source`; it identifies a device type, not where the employee was. Never invent data about another organisation, GPS coordinates, photographs, or face embeddings because the connector does not expose them.