Tools overview

The Dime.Scheduler MCP server groups its tools into seven categories. Every tool listed here is callable through the standard MCP tools/call method by any connected client.

Category	Tools	What it's for
Tasks & Jobs	search_tasks, search_jobs	Search work by id, name, or category.
Resources	search_resources, get_resource_details, get_resource_availability, find_available_slots, check_time_slot_availability, get_recommendations, find_resource_by_skill	Discover resources, check availability, match skills to jobs.
Appointments	get_resource_planning, search_appointments, get_appointment_details, create_appointment, update_appointment, reschedule_appointment, delete_appointment, change_appointment_time, change_appointment_resources, bulk_reschedule_appointments, bulk_delete_appointments, get_next_appointment	Read, create, change, and remove planned work - one at a time or in batches.
Optimization	optimize_field_service	Generate optimal route and assignment plans for a set of resources.
Time registration	get_timesheet, get_tracked_time	Read logged hours and the raw timer sessions behind them.
Messaging	send_message, search_notifications, create_notification	Notify users in real time, inspect notifications attached to entities, and log new ones.
Utilities	get_session_context, parse_relative_time	Ground the session in a timezone and identity; convert relative date phrases into concrete ranges.

Data the agent reads, not calls

Master data lookups (open tasksOpen taskA task that has not been scheduled yet. It waits in the open task list to be placed on the planning board., full resource roster, GPS pings, categoriesCategoryA visual indicator (a color) applied to appointments to classify or label them., time markersTime markerA visual indicator on an appointment, separate from its category, used to flag a status or condition at a point in time., recent notificationsNotificationA message from the back office attached to a task, an appointment or the whole tenant. The notifications component lists them, and a colored vertical bar on the appointment signals their severity., recommendation scorers) are exposed as data sources, not tools - the agent reads them via dimescheduler://... URIs without consuming a tool call.

Conventions

These conventions apply across the whole catalog. Knowing them up front makes the per-tool documentation easier to follow.

Time

• All date and time parameters are ISO 8601 strings.
• Most tools that span a date range require an explicit timeZone parameter - pass an IANA identifier like Europe/Brussels.
• Weeks start on Monday, not Sunday, when the parse_relative_time tool resolves expressions like "this week".
• When in doubt about a relative phrase, call parse_relative_time first and feed the resolved range into the next tool.
• Call get_session_context once at the start of a conversation. It returns the effective timezone and what "today" is; tools with an optional timeZone then fall back to the user's profile timezone, then the organization default.

Resources

ResourcesResourceAn entity that can carry out work - a person, vehicle, tool, or room - that you schedule on the planning board. are identified by their display name (e.g. John Smith), not by an internal ID. Where multiple resources are accepted, the parameter is a comma-separated string: John Doe, Jane Smith.

Appointments

AppointmentsAppointmentA task scheduled to a resource for a specific period - the scheduled instance you see on the planning board. can be identified in several ways depending on what the assistant knows: by appointmentNo (the most precise), by taskNo plus a date, or by subject plus startDateTime. When several appointments could match, also pass resourceDisplayName to disambiguate.

Limits

Read tools that return collections accept a limit parameter (defaulting to 100, or 500 for search_appointments). Increase it cautiously - large result sets are slow for the assistant to reason about.

Permissions

The MCP server only exposes data that the API key's owner is allowed to see. If a tool returns no results where you expected some, check the user's roleUser roleA named bundle of user actions assigned to users and user groups. Permissions flow through roles, never directly to a user. and resource visibility in Dime.Scheduler before assuming a bug.

Choosing the right tool

Use this guide to pick the right tool for common decisions:

• Searching for unknown resources that match skills? → get_recommendations, or find_resource_by_skill when you just need "who can do X?" without dates or location.
• Looking for a free slot for a known resource? → find_available_slots.
• Validating one specific time? → check_time_slot_availability.
• Moving an existing appointment? → reschedule_appointment, not get_recommendations. With the appointmentNo in hand and only one thing to change, change_appointment_time or change_appointment_resources is narrower.
• What's next for a resource? → get_next_appointment.
• Leaving a note on a job, task, or appointment? → create_notification; use send_message to reach a person right now.
• Need to know what's already scheduled? → get_resource_planning or search_appointments.