Partelisto

Reviewed 1d ago.

• tools: 8 tools scanned
• metadata: scanned

No findings.

Tools (8)

• create_booking

  Creates a new booking (a check-in workflow) for one of the host's properties. Requires the write permission granted separately during sign-in. Ask the host to confirm the property and dates before calling this. Does not email the guest — call send_guest_checkin_link afterwards if a link should go out now.

• send_guest_checkin_link

  Sends (or resends) the guest check-in link by email for a booking the host owns. This is a real action with a side effect: it emails the guest and, on resend, invalidates the guest's previous link. Requires the write permission granted separately during sign-in. Ask the host to confirm before calling this.

• list_ses_statuses

  SES.HOSPEDAJES (police registration) submission status for a set of bookings the host owns: status, attempts, last error, and the official reference once accepted. Bookings with no submission yet are omitted.

• get_guest_form_status

  Whether the guest has completed the check-in form for a booking the host owns (None or Submitted). No form content.

• list_bookings

  Lists the signed-in host's bookings (newest first), paged. Returns id, property id, check-in/check-out dates, status, and whether a check-in link and guest contact exist — never the guest's email, phone, or documents.

• get_attention_required

  Scans the signed-in host's most recent bookings (up to 50) and returns only what needs action right now: stays that are imminent or under way where the guest has not completed check-in, and bookings whose SES.HOSPEDAJES submission failed. Empty list means nothing needs attention within the window. No guest PII.

• list_properties

  Lists the signed-in host's properties: id, name, address, municipality/province, and whether it is archived. No guest data.

• get_usage_summary

  The signed-in host's plan tier, trial status, and this month's usage against plan limits (properties, templates, bookings).