> ## Documentation Index
> Fetch the complete documentation index at: https://docs.daysync.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Example Prompts

> Things worth asking once the Daysync MCP server is connected.

You never name tools — ask in plain language and the client picks them. These are prompts that work well in practice, grouped by what you are trying to get done.

<Tip>
  Start by naming the tour. *"On the Spring 2026 tour, …"* saves the client a round of searching, because almost every tool needs a tour ID first.
</Tip>

***

## Getting oriented

> Which Daysync account am I connected as?

> List my Daysync organizations and the tours in each.

> Give me a summary of the Spring 2026 tour — how many days, and what's on each.

> What's happening on 14 March?

## Day-to-day questions

> What time is load-in in Melbourne?

> Which venues on this tour still have no capacity set?

> List every travel item next week with its origin and destination.

> Are there any schedule items still unconfirmed on the Sydney day?

> Who's on the guest list for Friday, and how many total guests is that?

> Which hotels are we in next week, and what are the check-in times?

## Making changes

<Note>
  Your client will ask before running anything that writes. Destructive tools are flagged, so deleting a tour or a tag prompts explicitly.
</Note>

> Add a press call at 2pm on the Sydney day, 30 minutes, in the venue's green room.

> Move soundcheck on 14 March from 4pm to 4:30pm.

> Mark everything on the Melbourne day as confirmed.

> Add these five items to the Brisbane day: …

> Create a tag called "Press" in red, and put it on both press calls this week.

> Add the venue's box office email to the Sydney venue: box@…

> Post a bulletin on the Perth day: doors have moved to 7:30.

## Working with tags

> What tags exist on this tour?

> Which items are tagged "Press"?

> How many items use the "Travel" tag? If it's unused, delete it.

## Chat (read-only)

> What's pinned in the production channel?

> Search the tour chat for "load in" and show me the most recent mentions.

> Summarise what was discussed in the production channel yesterday.

> Has anyone shared the stage plot in chat?

<Note>
  Chat is read-only, and 1:1 direct messages are never available — only channels and group chats. See [Chat](/endpoints/chat).
</Note>

## Multi-step work

The things that genuinely save time are the ones that would be several screens in the app:

> Compare the Sydney and Melbourne days and tell me what's different about the schedule.

> Find every day next month with no accommodation booked.

> Go through the tour and list any venue missing a contact email.

> Copy the structure of the Sydney day onto the Brisbane day, shifting everything an hour later.

> Check the guest list for duplicates across the week.

***

## Getting better answers

**Be specific about the day.** *"the 14th"* is ambiguous across a long tour; *"14 March"* or *"the Melbourne day"* is not.

**Ask it to confirm before bulk changes.** *"Show me what you're about to change first"* works, and is worth it when touching a whole day.

**Narrow big reads.** On a long tour, *"load the whole tour"* can be more than the client will comfortably hold. Ask for a date range or a single day.

**If a tool seems missing,** it is almost always scope or a stale session — see [Troubleshooting](/mcp/troubleshooting).

***

See also: [Tool catalogue](/mcp/tools) · [Common Workflows](/common-workflows) for the REST equivalents.