TimeZest Appointment Types — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited TimeZest Appointment Types (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
An appointment type defines what kind of meeting a TimeZest booking is — its name, its duration, and the availability rules behind it. Picking the wrong type produces a customer-facing mistake: a 15-minute "Quick Call" type used for a half-day onsite books a slot that is far too short.
Enter the domain with timezest_navigate to appointment_types.
| Tool | Purpose |
|---|---|
timezest_appointment_types_list | List all appointment types available for scheduling |
timezest_appointment_types_get | Get full detail for one type by appointmentTypeId |
timezest_appointment_types_list accepts pageSize (1–100, default 50) and a filter TQL string (e.g. active:true).
Each appointment type carries at least:
id — the appointmentTypeId used in a scheduling requestname — e.g. "Onsite Visit", "Remote Session", "Discovery Call"duration — slot length in minutesdescription — optional free-text detail| Ticket / intent | Typical appointment type |
|---|---|
| Remote support session | "Remote Session" |
| Field dispatch to the customer site | "Onsite Visit" |
| Scoping or pre-sales conversation | "Discovery Call" |
| Short follow-up | "Quick Call" |
These names are tenant-configured — always read the actual list rather than assuming a naming convention.
timezest_navigate to appointment_types.timezest_appointment_types_list with active:true.name and duration fit the ticket's work.timezest_appointment_types_get to read the full description.
appointmentTypeId intotimezest_scheduling_create_request.
pageSize: 100.dispatcher knows the menu before booking.
the full list to the dispatcher rather than booking a mismatched type. A wrong duration is visible to the customer.
duration matches theexpected work length; type names can be misleading.
active:true; deactivated types stillappear in an unfiltered list but cannot be booked.
listcall every session — do not cache the ID.
timezest_scheduling_create_request is called without anappointment type, the MCP server elicits a choice; pre-resolving it here avoids that round-trip and keeps the booking deterministic.
duration both fit.
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.