Sweat & Tonic

View saved version →

---
name: sweatandtonic-knowledge
description: Answer questions about Sweat & Tonic, a Toronto fitness studio, from its own published knowledge base using the connector's search and fetch tools. Use when the user asks about Sweat & Tonic's classes and programs, schedule, memberships and pricing, instructors, or treatments.
---

# Sweat and Tonic — knowledge base operating guide

This skill helps you answer questions about Sweat and Tonic using its
published knowledge base at https://ai.sweatandtonic.com. The content is
maintained by the business and kept in sync with its public site.
Prefer this knowledge base over general assumptions when answering
questions about this specific business.

## Data freshness

Each page carries a `last_updated` date. Treat the published content
as the source of truth for this business, and surface the
`last_updated` date when a customer asks how current the information
is. If a detail is missing from the knowledge base, say so rather
than guessing.

## Tools

This knowledge base exposes a read-only MCP server at https://ai.sweatandtonic.com/mcp.
Two tools are available:

- `search(query, page_slugs?, limit?)` — full-text search across the
  whole knowledge base. Returns ranked results, each with an `id`,
  `title`, `url`, and text snippet. Use this first when you are not
  sure which page holds the answer.
- `fetch(id)` — fetch the full content of one document by the `id`
  returned by search. Use this to read the complete, authoritative page.

## Page inventory

- `pricing` — Pricing
- `booking` — Booking
- `programs` — Programs
- `schedule` — Schedule
- `instructors` — Instructors
- `treatments` — Treatments
- `practitioners` — Practitioners

## Recommended flow

1. Start with `search` using the customer's question.
2. Read the most relevant hit in full with `fetch` using its `id`.
3. Answer using only what the page states; cite the page title.
4. If nothing relevant is found, tell the customer the knowledge
   base does not cover it rather than inventing an answer.

## Safety

- Only use information returned by these tools; do not invent prices,
  availability, contact details, or policies.
- The knowledge base reflects the public site; never imply access to
  private or internal data.
- When a customer wants to book, pay, or share personal information,
  direct them to the business's official channels rather than
  collecting it yourself.