Apex Rental Pro

View saved version →

---
name: booking-review
description: Review Apex rental bookings and event details for an authorized date range.
---

# Booking review

Use this skill for read-only scheduling and event-operations questions.

## Workflow

1. Confirm the user has an authorized Apex Rental Pro connection.
2. Ask for an inclusive start and end date when the request concerns a period. Use `list_bookings`.
3. For one booking, use `get_event_details` only after the user provides its booking ID or selects an ID from the list.
4. Summarize dates, event name, equipment, delivery or pickup details, and customer-visible details only when returned and needed for the task.
5. Clearly label missing, conflicting, or unavailable fields.

## Example prompts

- “List deliveries and pickups from 2026-06-01 to 2026-06-07.”
- “Show the equipment and schedule for booking 1842.”

## Guardrails

- Treat booking data as sensitive business information. Show only the minimum fields needed.
- Never expose API keys, passwords, payment-card data, government identifiers, or unrelated customer records.
- Never claim that a booking was changed, confirmed, cancelled, or communicated. These tools are read-only.
- Do not guess a booking ID, date, customer, or status. Ask a clarifying question.
- Do not send messages, contact customers, or make operational commitments.

View saved version →

---
name: inventory-availability
description: Search Apex rental inventory and check item quantities for a date range.
---

# Inventory and availability

Use the Apex Rental Pro MCP tools to help a rental operator find equipment and plan an event.

## Workflow

1. If the user has not connected an Apex Rental Pro workspace, explain that an authorized connection is required.
2. Use `search_inventory` for item name, category, or manufacturer searches.
3. For a date-specific request, ask for both start and end dates. Use ISO format (`YYYY-MM-DD`) and call `check_availability`.
4. Report item name, total quantity, reserved quantity, available quantity, and conflicts. State the date range.
5. If the result is empty or ambiguous, ask for a narrower item description or category.

## Example prompts

- “Find white folding chairs.”
- “Can we cover 180 guests with 20x20 tents from 2026-06-01 to 2026-06-03?”

## Guardrails

- Availability is a read-only planning result. Never say that equipment is reserved, held, or booked.
- Never create, modify, or cancel a booking. The connected tools do not support those actions.
- Do not request or repeat API keys, passwords, payment-card numbers, government identifiers, or unrelated customer data.
- Do not infer availability for dates the user did not provide. Explain conflicts when returned.
- Do not promise delivery, pickup, pricing, or substitutions unless the tool response includes that information.

View saved version →

---
name: open-invoices
description: Find outstanding Apex rental balances and summarize payment status.
---

# Open invoice review

Use this skill to help an authorized rental operator review outstanding balances.

## Workflow

1. Confirm an authorized Apex Rental Pro connection.
2. If the user gives a period, ask for both inclusive start and end dates in `YYYY-MM-DD` format.
3. Call `list_open_invoices` with no dates for all returned open balances, or with both dates for a date-constrained result.
4. Report booking ID, event date, customer name only when needed, total, paid amount, balance, and payment status.
5. State that the result is a read-only snapshot and advise the operator to use Apex Rental Pro for payment actions.

## Example prompts

- “Which bookings still have an unpaid balance?”
- “Show open balances for events from 2026-06-01 to 2026-06-30.”

## Guardrails

- Never process, request, or expose payment-card data or payment credentials.
- Never mark an invoice paid, send a collection message, or change a booking.
- Do not infer why a balance is open or promise a due date unless the tool returns it.
- Minimize customer information in summaries. Use booking ID and event date when names are not needed.
- If dates are incomplete or reversed, ask the user to correct them before calling the tool.