AI Projects / Badminton Court Booking Agent

Subang Badminton Arena · Booking Assistant

A court booking assistant that answers only from the centre's policies (fictional data) ·

The system

Claude talks to the player. Everything it may say about rules comes from three policies, each clause with an ID, and everything it can do goes through nine MCP tools. The rules that must never break are checked in the tools' code. Every money decision, confirmation, release and refund stays with staff, one click on the dashboard, and each click sends a fixed message back into the player's chat.

PlayerAsks in the chat: prices, free courts, a booking, a receipt, a cancellation, anything else.
⇄
Claude (the assistant)Decides which of four cases the question is, picks the tool, writes the reply with its clause citations.
Covered: answer. Contradicts: decline. Not covered or unclear: hand to staff.
⇄
MCP server
3 resources (read)Operation, Booking and Cancellation policies
9 tools (act)check_availability · request_booking · verify_booking · get_booking · report_payment · quote_cancellation · request_cancellation · hand_to_staff · reply_to_player
→
Staff dashboardFollow up: only what needs a person (receipts, expired holds, cancellations, handovers). Courts: the next 7 days. Staff confirm against the bank record.
↩ Staff clicks send fixed messages straight into the player's chat (confirmed, payment not received, hold released, cancellation approved), and staff replies to handovers arrive there too.

What has no tool cannot happen: no tool confirms, cancels, releases, refunds or changes a booking, and none lists bookings or names a player.

How it handles each kind of enquiry

PlayerClaudeResource or toolRule in codeStaff

Staff actions and the messages they send

Written in code, triggered by a staff click, delivered live into the player's chat. The assistant never writes them.

MCP resources

The three policies the assistant reads, loaded at the start of each conversation and cached. Every clause has an ID; citations link to the clause in the published policy page.

MCP tools

Each tool checks its own rules in code and returns a named error the assistant can act on: fix the input, ask the player, offer the alternatives, or hand to staff.

Benchmark result

Make a booking, upload a receipt, then press Confirm on the dashboard: the confirmation arrives in this chat.

Your Anthropic API key

Before you paste a key: usage is billed to your own Anthropic account, so use a key with a spending limit. The key stays in this tab's memory and goes only to Anthropic. A public service would send requests through its own server instead.

Limits per conversation: 15 messages, 700 output tokens and 8 tool rounds per reply.

Demo receipts

Try asking

Bookings, receipts and handovers are saved in this browser and shared with the staff dashboard.