Tools overview

Preview

The MCP integration is in preview - tools, parameters, and behavior may change between releases.

The Dime.Scheduler MCP server groups its tools into four 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	get_open_tasks, search_tasks, search_jobs	Find work that needs to be planned.
Resources	list_resources, get_resource_details, get_resource_availability, find_available_slots, check_time_slot_availability, get_recommendations	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	Read, create, change, and remove planned work.
Reference data & utilities	list_categories, list_time_markers, parse_relative_time	Look up master data and convert relative dates into concrete ranges.

Conventions

A handful of 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.

Resources

Resources 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

Appointments 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 role and resource visibility in Dime.Scheduler before assuming a bug.

Choosing the right tool

A few common decisions:

• Searching for unknown resources that match skills? → get_recommendations.
• 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.
• Need to know what's already scheduled? → get_resource_planning or search_appointments.