Tool Catalogue

The server knows 140 operations, and by default it advertises 26 of them as tools. The rest are fully available — you reach them through three discovery tools instead of having all 140 definitions loaded into every conversation. You only ever see or reach operations covered by the scopes you approved at connect time — a read-only connection never shows a tool that writes, and discovery does not change that.

✓ in the Tool column means the operation is advertised as a tool by default. Everything else is reached via invoke_operation.⚠️ marks operations annotated as destructive. Well-behaved clients — including Claude — ask before running these.You do not need to memorise names. Ask in plain language and the client picks the operation — the names are here for debugging and for writing your own client.

The discovery model

Advertising every operation cost about 33,000 tokens of tool definitions back when there were 106 of them — before the client had read a single word of your question — and near-neighbours (create_schedule_item vs. create_schedule_items) made the choice ambiguous. With 140 it would be worse. The default surface stays small and the long tail is fetched on demand.

Tool	What it does
`list_capabilities`	Call it with no arguments for the domains and how many operations each holds; call it with `domain` for that domain’s operation names, one-line summaries, and read / destructive / idempotent flags. This is how you find an operation that is not in the tool list.
`describe_operations`	Returns the exact typed input (and output) for named operations — the same JSON Schema you would have seen had they been advertised. Ask for at most 10, and only the ones you are about to use.
`invoke_operation` ⚠️	Runs one: `{ operation, input }`. Input is validated against that operation’s real schema, so a wrong shape is rejected with the expected fields rather than half-applied.

So the write flow is: list_capabilities → describe_operations → invoke_operation. invoke_operation cannot call arbitrary URLs or endpoints. operation must name an operation in this catalogue, and one your connection is authorised for; anything else is refused.

Keeping the old tool list

If your client enumerates tools and you want everything advertised, append ?tools=all to the MCP URL (or send x-daysync-mcp-tools: all) to get all 140 as tools. Nothing is ever removed: every tool name that has existed is still callable by name, whether or not it appears in tools/list. An integration that hardcodes create_pass_type needs no change.

Where to start

A few tools do most of the work:

Tool	Why it matters
`list_organizations` → `list_tours`	How you find IDs. Nearly every other operation needs a tour UUID.
`search_tour_content`	Find something when you don’t know which day — or even which tour — it’s on. Searches schedule items, venues, stays, guests, files and bulletins by name in one call.
`get_tour_data`	Loads a whole tour — every day with its date, name, day type, time zone and location, plus its schedule, venues, stays, guest lists and bulletins — in one call.
`list_reference_types`	Returns the ID lookups in one call. Needed before most writes.
`list_capabilities`	Finds anything not in the tool list. Cheap; safe to call whenever you are unsure a capability exists.
`whoami`	Confirms which Daysync account you are connected as.

Session & users

Operation	Tool	What it does
`whoami`	✓	Shows the account this connection is bound to — email, name and subject id.
`disconnect` ⚠️	✓	Revokes this connection; the next request prompts a fresh sign-in.
`list_capabilities`	✓	See discovery.
`describe_operations`	✓	See discovery.
`invoke_operation` ⚠️	✓	See discovery.
`get_tour_structure`		The parties, subgroups and splits of a tour, with live member counts.
`get_tour_personnel`		The full roster — members, pending invites and open roles — with each person’s visibility, edit reach, editable kinds, and whether they manage personnel.
`preview_structure_delete`		What deleting a party, subgroup or split would affect, without deleting anything.
`get_item_aims`		Who an item is aimed at right now, with group identity preserved. Read it before changing an audience.

whoami and disconnect are always available on any connection.

Files

tours.read to read, schedule.write to upload and attach. All four are advertised by default, because they are the only route to file content.

Operation	Tool	What it does
`list_files`	✓	List the files attached to a tour — across its schedule items, venues, stays and pass types — with ID, name, size, which entity holds it and when it was added. Filter by `entityTypes`, `dayId` or a file-name `search`; page with `limit`/`offset` (max 200).
`get_file`	✓	Metadata plus a short-lived signed download URL for one file. The URL expires in about five minutes — fetch it or hand it over straight away, and call again for a fresh one rather than storing it.
`upload_file`	✓	Stores a file and returns the key to attach. Three sources, see below. Idempotent.
`attach_file`	✓	Attaches an already-uploaded file to a schedule item, venue, stay or pass type. Additive — it never touches the entity’s existing attachments.

Choosing an upload source

upload_file takes a source:

`source`	Use it when	Notes
`content`	You have the bytes	Base64, max 256 KB. The only source an assistant can drive on its own.
`url`	The file is at a public HTTPS URL	The server fetches it (max 25 MB). Direct links only — redirects are refused.
`ticket`	The file is large and local to your app	Returns a signed `PUT` URL. Send the returned headers exactly as given: `content-length` and `content-type` are part of the signature, so storage rejects anything else. An assistant cannot do this itself.

Uploading does not attach anything — call attach_file next.

Bulletins do not support attachments. Chat files are not in list_files either; use search_chat_files.Prefer attach_file over re-sending an entity’s update body with attachments, which replaces the whole set.

Limits and rejections

Rule	Result
Content type not on the allow-list (images, PDF, Office documents, text/CSV, ZIP, audio, video)	`415` naming the allowed types. SVG, HTML and executables are not allowed.
Inline upload over 256 KB	`413` naming the two larger-file alternatives.
File over 25 MB	`413`.
A key that this API did not mint	`400`. Arbitrary or traversing storage paths are not accepted.
A key that was never uploaded, or whose ticket expired	`404`.
An entity that is not on the named tour, or that you cannot see	`404` / `403`.

File reads are bounded by the same organization, tour, role and per-item visibility rules as everything else: a file on a private item you are not on is not listed, and files on another tour are not reachable.

Organizations

organization.read — read-only.

Operation	Tool	What it does
`list_organizations`	✓	List the organizations the authenticated Daysync user belongs to.
`list_organization_members`		List the members of an organization.
`list_org_key_contacts`		List the organization’s key-contact book — the people who can be linked to venues and stays.

Tours

tours.read / tours.write.

Tours, days and lookups

Operation	Tool	What it does
`list_tours`	✓	List tours in an organization as memberships (`role`, `member_count`, `tour`).
`list_tour_members`	✓	List the members of a tour. The ungated, lighter read — `get_tour_personnel` has the detail.
`get_tour_data`	✓	Load a whole tour in ONE call: every day with its schedule items, venues, stays, guest lists, bulletins and pass types, plus per-day counts.
`search_tour_content`	✓	Search schedule items, venues, stays, guests, files and bulletins by name. Scope `TOUR` searches one tour; `ORG` searches every tour you can reach in that org (never another org), archived tours included by default. Results are ranked, grouped by kind with exact totals, and carry `dayId` + `section` + `navigateItemId` to locate each hit.
`list_reference_types`	✓	Look up the ID values the create/update operations require.
`list_day_types`		List the available day types.
`create_tour`		Create a tour with its days (at least one).
`update_tour` ⚠️		Update a tour. Days you do not mention are preserved; deletions must be explicit.
`delete_tour` ⚠️		Soft-delete a tour.

Day sheet

Operation	Tool	What it does
`get_day_sheet_data`		Read one tour day as a print-ready day sheet model: header, running order, venues, stays, consolidated key contacts, guest-list totals, bulletins and the upcoming-days strip. Use it to decide what to include before exporting.
`export_day_sheet`		Render one tour day as a PDF day sheet and return a short-lived download URL.

The day sheet is a read, despite export_day_sheet being a POST. It rides tours.read, creates nothing on the tour, and changes no record — the POST is only because the render takes a body. Start from a preset (FULL, SCHEDULE, MINIMAL) and narrow it with options; ids you pass that you cannot see are dropped and counted in ignoredIdCount. See Day sheet.

get_tour_data, search_tour_content, get_day_sheet_data, export_day_sheet, list_files and get_file each span several resources, so they need the read scope for all of them — see Scopes. They appear with tours.read but fail without the rest.

Structure and personnel

A tour’s structure is its parties (top level, e.g. Band, Audio), subgroups under a party, and splits — cross-cutting groups like Bus A or Early flight. Personnel can belong to any combination, and items can be aimed at any of them.

Operation	Tool	What it does
`create_tour_party`		Create a party. Not idempotent — repeating it makes a second party with the same name, so read `get_tour_structure` first.
`create_tour_subgroup`		Create a subgroup under a party.
`create_tour_split`		Create a split.
`update_structure_group` ⚠️		Rename a party, subgroup or split, or change its colour, order, or (subgroups) whether it shares to its parent party.
`delete_structure_group` ⚠️		Delete a party, subgroup or split. Run `preview_structure_delete` first.
`create_open_role`		Create a seat on the roster with nobody in it, so counts, coverage and aims are right before the hire lands.
`add_tour_member`		Attach someone already in the organization to this tour at a seat (1 org admin, 2 editor, 3 viewer). Costs no paid seat, and never adds anyone new to the organization.
`fill_open_role` ⚠️		Put an existing organization member into an open role.
`remove_tour_personnel` ⚠️		Remove somebody from the tour.
`set_personnel_memberships` ⚠️		Set which party, subgroups and splits somebody belongs to.
`set_personnel_access` ⚠️		Set somebody’s access: what they can see, how far their editing reaches, which kinds of thing they may edit, whether they manage personnel, and whether they manage the tour itself.
`update_personnel_details` ⚠️		Update somebody’s job title, or an open role’s name and note.

Personnel operations need the personnel-management permission on the tour (or an organization admin role). Without it, get_tour_personnel and the writes answer 403 — list_tour_members still works.

Visibility: aims and seals

Every schedule item (travel included — a flight is a schedule item), venue, stay and pass type has an audience.

Operation	Tool	What it does
`set_item_aims` ⚠️		Set the complete audience, replacing what is there. Targets can be a party, subgroup, split, person or pending invite. An empty array makes the item public — it does not hide it. `times_only` (schedule items only) shows the real title and time and nothing else.
`seal_item` ⚠️		Seal an item: visible to the people named on it and nobody else — not even an unnamed org owner. Absent from every count and day sheet for everyone else. You are named automatically; open roles can’t be named.
`unseal_item` ⚠️		Remove a seal, returning the item to ordinary aim-based visibility.
`set_seal_names` ⚠️		Replace the list of people who may see a sealed item.

Group targets follow membership; individual targets don’t. A viewer reached by several paths gets the strongest level.

Schedule

schedule.read / schedule.write.

Items

Operation	Tool	What it does
`get_schedule`	✓	Get the schedule items for a specific tour day.
`create_schedule_item`		Create a schedule item on a tour day.
`create_schedule_items`		Create many items in one call — use this instead of looping.
`update_schedule_item` ⚠️		Update a schedule item.
`delete_schedule_item` ⚠️		Delete a schedule item.
`restore_schedule_item`		Restore a soft-deleted schedule item.
`confirm_all_schedule_items` ⚠️		Mark every schedule item on a day as confirmed.
`get_item_custom_fields`		Get a schedule item’s custom fields.
`set_item_custom_fields` ⚠️		Add, update or remove a schedule item’s custom fields.
`upload_attachment`		Upload a file by URL. Superseded by `upload_file` (`source: "url"`); kept for compatibility.

Operation	Tool	What it does
`list_tags`	✓	List the tags defined on a tour, with their colours.
`create_tag`		Create a tag on a tour.
`update_tag` ⚠️		Rename a tag or change its colour.
`delete_tag` ⚠️		Permanently delete a tag — a hard delete, removed from every item.
`get_tag_usage`		Count how many items carry a tag — use before `delete_tag`.
`set_item_tags` ⚠️		Set the tags on a schedule item (replaces the whole set).

Flights

Operation	Tool	What it does
`search_flights`		Look up a real flight by number (`QF1`, `BA16`) across the day before, the day, and the day after. Read `data.status` first: `OK`, `NO_RESULTS` (usually a typo), `NOT_OPERATING` (real flight, wrong dates — `operatingWeekdays` says when it flies), `TAIL_NUMBER` (resend with `treatAsFlightNumber: true`), or `INVALID_QUERY`. Only touches your recent-search list.
`list_recent_flight_searches`		Your last five flight numbers searched on this tour, newest first.
`attach_flight` ⚠️		Attach a searched flight to a tour day — creating the item, or re-connecting an existing one. A multi-leg `SERVICE` creates one item holding every leg. Idempotent.
`get_flight_legs`		The stored legs of a flight item, in order — stops, terminals, coordinates, airport addresses and per-leg times (UTC).
`disconnect_flight` ⚠️		Remove the link to the lookup but keep every value it filled in, so a human can edit them.
`clear_flight` ⚠️		Remove the link and every value the flight filled in, leaving an empty flight ready to search again.

Vehicles and drive routing

Operation	Tool	What it does
`list_tour_vehicles`		List the saved vehicles on a tour, with dimensions. Get a `vehicleProfileId` here before routing. A drive with no vehicle routes as Car (default).
`create_tour_vehicle`		Save a vehicle so drives route for its size, weight and speed.
`update_tour_vehicle` ⚠️		Change a saved vehicle.
`delete_tour_vehicle` ⚠️		Retire a vehicle. Run `get_vehicle_usage` first.
`restore_tour_vehicle`		Undo a delete — bring the vehicle back and put its drives back on it.
`get_vehicle_usage`		Count the drives currently routed as a vehicle.
`calculate_drive_route`		Calculate a drive’s arrival time, duration and distance for a vehicle and a set of avoided road types.

Templates

Operation	Tool	What it does
`list_schedule_templates`		List your saved schedule templates for a tour.
`get_schedule_template_items`		Read the items a template holds.
`save_schedule_template`		Save a set of existing schedule items as a reusable template.
`rename_schedule_template` ⚠️		Rename a template. The only edit possible — its items are fixed at save time.
`delete_schedule_template` ⚠️		Soft-delete a template. Items created from it are unaffected.
`restore_schedule_template`		Restore a soft-deleted template, with its items.
`apply_schedule_template` ⚠️		Create a template’s items on a tour day. `REPLACE` mode soft-deletes the day’s existing visible items first.
`undo_applied_schedule_template` ⚠️		Soft-delete the items a template created on a day.

Schedule templates are per user. list_schedule_templates shows only the connected account’s own templates, and a template can only be applied to a day of the tour its items came from. See Schedule Templates.

Venues

venues.read / venues.write.

Operation	Tool	What it does
`list_venues`	✓	List the venues for a tour.
`get_venue`	✓	Get one venue in full — custom fields, contacts, age restriction, visibility.
`create_venue`		Create a venue on a tour day.
`update_venue` ⚠️		Update a venue.
`delete_venue` ⚠️		Delete a venue.
`get_venue_contacts`		Get a venue’s own emails, phone numbers and URLs.
`set_venue_contacts` ⚠️		Add, update or remove a venue’s emails, phone numbers and URLs.
`get_venue_custom_fields`		Get a venue’s custom fields.
`set_venue_custom_fields` ⚠️		Add, update or remove a venue’s custom fields.
`get_venue_key_contacts`		Get the contact-book people linked to a venue.
`set_venue_key_contacts` ⚠️		Link or unlink contact-book people on a venue.
`list_age_restrictions`		List venue age restrictions.
`list_venue_field_templates`		List the premade venue custom-field templates.

Accommodation

accommodation.read / accommodation.write.

Operation	Tool	What it does
`list_accommodation`	✓	List the accommodation for a tour.
`get_accommodation`	✓	Get one stay in full — custom fields, contacts, visibility.
`create_accommodation`		Create an accommodation stay.
`update_accommodation` ⚠️		Update an accommodation stay.
`delete_accommodation` ⚠️		Delete an accommodation.
`get_stay_contacts`		Get a stay’s own emails, phone numbers and URLs.
`set_stay_contacts` ⚠️		Add, update or remove a stay’s emails, phone numbers and URLs.
`get_stay_custom_fields`		Get a stay’s custom fields.
`set_stay_custom_fields` ⚠️		Add, update or remove a stay’s custom fields.
`get_stay_key_contacts`		Get the contact-book people linked to a stay.
`set_stay_key_contacts` ⚠️		Link or unlink contact-book people on a stay.
`list_rooms`		List a stay’s rooms with their occupants and pending invites.
`create_room` ⚠️		Add a room to a stay.
`update_room` ⚠️		Update a room.
`delete_room` ⚠️		Soft-delete a room.
`restore_room`		Restore a soft-deleted room.
`create_key_contact`		Add a person to the organization’s key-contact book.
`update_key_contact` ⚠️		Update a person in the key-contact book.
`list_stay_field_templates`		List the premade stay custom-field templates.

Guest list

guestlist.read / guestlist.write.

Operation	Tool	What it does
`get_guest_list`	✓	Get the guest list for a specific tour day.
`list_pass_types`	✓	List a tour’s pass types (needed to add guests).
`add_guest`		Add a guest-list entry to a tour day.
`update_guest` ⚠️		Update a guest-list entry — send the full record, not a delta.
`update_guest_statuses` ⚠️		Approve, deny or waitlist entries in bulk. All-or-nothing across the batch.
`delete_guest` ⚠️		Delete a guest-list entry. Reversible with `restore_guest`.
`restore_guest`		Restore a soft-deleted guest-list entry, with its pass allocations.
`get_approved_guest_count`		The approved-guest total for a day — a sum of party sizes, not a row count.
`set_guestlist_config` ⚠️		Set a day’s guest cap, lock, cut-off and per-pass-type caps. Requires tour-admin.
`list_guestlist_requesters`		List the users who can be a guest-list entry’s requester.
`create_pass_type`		Create a pass type on a tour. Requires tour-admin.
`update_pass_type` ⚠️		Update a pass type — a full record; `day_ids` replaces the day set. Requires tour-admin.
`delete_pass_type` ⚠️		Soft-delete a pass type. Without `force` it is a safe check that deletes nothing and returns the blocking guests.
`restore_pass_type`		Restore a soft-deleted pass type, with the allocations removed alongside it.

Prefer update_guest_statuses over looping update_guest, which requires the guest’s whole record on every call. And read delete_pass_type’s response rather than only its success: without force it deliberately deletes nothing when a guest still holds the pass.

Bulletins

bulletins.read / bulletins.write. Bulletins are aimed items, filtered by the same visibility rules as everything else.

Operation	Tool	What it does
`list_bulletins`	✓	List the bulletins for a tour.
`create_bulletin` ⚠️		Create a bulletin on a tour day (the tour is resolved from the day).
`update_bulletin` ⚠️		Update a bulletin.
`delete_bulletin` ⚠️		Soft-delete a bulletin.

Chat

chat.read — read-only, and 1:1 direct messages are never exposed. See Chat.

Operation	Tool	What it does
`list_conversations`	✓	List the tour’s channels and group chats you belong to, with unread counts and last message.
`get_messages`	✓	Read a conversation’s messages, newest first.
`is_chat_enabled`		Check whether chat is switched on for a tour.
`get_conversation`		Get one channel or group chat.
`list_conversation_members`		List who is in a channel or group chat.
`get_thread_replies`		Read the replies on a threaded message, oldest first.
`list_pinned_messages`		List a conversation’s pinned messages — usually load-in details, addresses and running order.
`get_message_reactions`		List the reactions on a message, grouped by emoji.
`search_chat`		Search a tour’s chat history for a phrase.
`search_chat_files`		Find files and images shared in a conversation.

Retrying a write safely

Operations flagged idempotent in list_capabilities accept an optional idempotency_key. Today that covers create_tour, create_schedule_item, create_schedule_items, create_venue, create_accommodation, create_room, create_key_contact, create_tag, create_tour_vehicle, create_pass_type, create_bulletin, add_guest, save_schedule_template, apply_schedule_template, attach_flight, upload_file and upload_attachment.


Reuse the same value	when retrying a call you are not sure completed. The original result comes back instead of a second record.
Use a new value	when you genuinely want another copy.
Omit it	and one is derived from the payload, so an identical retry within about ten minutes is treated as the same action.

That last row is why a duplicated tool call — the failure mode a retrying agent is most prone to — does not silently create two schedule items.

The structure and personnel creates (create_tour_party, create_tour_subgroup, create_tour_split, create_open_role, add_tour_member) are not idempotent. Read get_tour_structure or get_tour_personnel before retrying.

Why a tool might be missing

It is not on the default surface. Most operations are not advertised as tools. Call list_capabilities to find it, then describe_operations and invoke_operation — or append ?tools=all to the MCP URL to advertise everything.
You did not consent to its scope. Reconnect and approve it. invoke_operation distinguishes this case explicitly: it answers INSUFFICIENT_SCOPE and names the scope needed, rather than telling you the operation does not exist.
The application does not hold that scope. Nothing you can do client-side — the partner credential needs it.
Your role doesn’t allow it. Personnel and some guest-list operations need tour-admin or personnel-management rights; these return 403.
Your session predates the tool. Tool lists are cached from session start; start a new chat.

See Troubleshooting.

When something new becomes a tool

So the surface does not creep back up, new capabilities follow a fixed rule:

If an existing tool covers it with one more field, that tool is extended.
Otherwise it becomes an operation — reachable via list_capabilities / describe_operations / invoke_operation from day one, with no client change and no re-consent.
It is promoted to an advertised tool only if an agent needs it to orient itself (a read), or it is the only route to a capability (files); its name is unambiguous against every other advertised tool; and its schema is small — a multi-kilobyte write body belongs behind describe_operations, which delivers it just in time.
Reference and lookup data stays bundled into one read rather than one tool per table.

search_tour_content is the most recent promotion under rule 3.

Every operation maps to a documented REST endpoint — see Scopes & Permissions for the mapping.

Getting Started

Dive Deeper

AI & MCP

The discovery model

Keeping the old tool list

Where to start

Session & users

Files

Choosing an upload source

Limits and rejections

Organizations

Tours

Tours, days and lookups

Day sheet

Structure and personnel

Visibility: aims and seals

Schedule

Items

Tags

Flights

Vehicles and drive routing

Templates

Venues

Accommodation

Guest list

Bulletins

Chat

Retrying a write safely

Why a tool might be missing

When something new becomes a tool

​The discovery model

​Keeping the old tool list

​Where to start

​Session & users

​Files

​Choosing an upload source

​Limits and rejections

​Organizations

​Tours

​Tours, days and lookups

​Day sheet

​Structure and personnel

​Visibility: aims and seals

​Schedule

​Items

​Tags

​Flights

​Vehicles and drive routing

​Templates

​Venues

​Accommodation

​Guest list

​Bulletins

​Chat

​Retrying a write safely

​Why a tool might be missing

​When something new becomes a tool

The discovery model

Keeping the old tool list

Where to start

Session & users

Files

Choosing an upload source

Limits and rejections

Organizations

Tours

Tours, days and lookups

Day sheet

Structure and personnel

Visibility: aims and seals

Schedule

Items

Tags

Flights

Vehicles and drive routing

Templates

Venues

Accommodation

Guest list

Bulletins

Chat

Retrying a write safely

Why a tool might be missing

When something new becomes a tool