com.volunteerreminder/mcp

Est-ce que com.volunteerreminder/mcp est sûr ?

Au dernier audit MCP Hub, le serveur MCP « com.volunteerreminder/mcp » est classé « Non encore testé ». Référencé dans l'annuaire. Seul le pentest comportemental fait foi, et il n'a pas encore été exécuté sur ce serveur. Le verdict est réévalué en continu ; consultez la fiche pour l'état à jour.

Méthode : MCP Hub analyse la description de chaque outil (couche 1) et, pour le verdict fort, exécute le serveur dans une micro-VM isolée avec leurres et réseau bloqué (couche 2). On publie des noms et des compteurs, jamais le contenu brut renvoyé par un outil.

Les 23 outils

• add_contacts≈ 783 tokens

  Add one or more volunteers to the roster in a single call. ALL-OR-NOTHING: if the batch would push the account past its plan's volunteer limit, or any contact references a group_id not on this account, NOTHING is added and the error names the limit/count/bad id so you can adjust. Phone numbers are validated and normalized to E.164. Adding a mobile number needs consent_attested=true (ask the user to confirm the volunteers agreed to texts). To put new volunteers on a shift, follow with assign_contacts_to_schedule. Requires the `contacts:write` scope.

  Paramètres, retour & exemple (2)

  Paramètres

  • contacts · array · requis
    The volunteers to add (1–200 per call). Each needs at least a full_name.
  • consent_attested · boolean · optionnel
    Required true when any volunteer here has a mobile_phone. Set it only after the user confirms these volunteers agreed to receive shift-reminder texts. Not needed for email-only volunteers.

  Exemple d'appel

  {"name": "add_contacts", "arguments": {"contacts": []}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"created": []}}

• archive_schedule≈ 244 tokens

  Archive (soft-delete) a schedule. It stops appearing in the active list and no further reminders go out for it, but past reminder history is preserved. This is reversible only from the dashboard. Confirm with the user before archiving. Requires the `schedules:write` scope.

  Paramètres, retour & exemple (1)

  Paramètres

  • schedule_id · integer · requis
    The schedule's numeric id (from list_schedules or get_schedule).

  Exemple d'appel

  {"name": "archive_schedule", "arguments": {"schedule_id": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"id": 1, "archived": true}}

• assign_contacts_to_schedule≈ 346 tokens

  Assign volunteers to a schedule. This REPLACES the schedule's entire roster — send the COMPLETE desired set of contact ids, not a delta (pass an empty array to clear it). Every id must belong to this account or the whole request is rejected with the offending ids named. Does not change occurrences. Requires the `contacts:write` scope.

  Paramètres, retour & exemple (2)

  Paramètres

  • contact_ids · array · requis
    The complete set of volunteer contact ids for this schedule (replaces any existing roster). Empty array clears the roster.
  • schedule_id · integer · requis
    The schedule to assign the roster to.

  Exemple d'appel

  {"name": "assign_contacts_to_schedule", "arguments": {"contact_ids": [], "schedule_id": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"contact_ids": [], "schedule_id": 1}}

• create_account≈ 505 tokens

  Start a new VolunteerReminder account for a human, using their email address. This does NOT finish signup and does NOT return an API key: it emails the person a verification link they must click to activate the account. Nothing can be built on the account and no reminders can ever send until they verify — and even then a new account starts in safe `test` mode (reminders reach only the owner, never volunteers) until a human turns on live sending from the dashboard. Idempotent: calling it again with the same email re-sends the link and creates no duplicate. After the user tells you they've verified, they mint an API key from the dashboard and reconnect this connector with it. Tell the user to check their email.

  Paramètres, retour & exemple (2)

  Paramètres

  • email · string · requis
    The account owner's email address. The verification / sign-in link is sent here; only the person who controls this inbox can activate the account. Required.
  • organization_name · string · optionnel
    Display name for the organization (becomes the account name). Optional — defaults to a placeholder the owner can rename after verifying. The account timezone defaults to America/Chicago and is editable later.

  Exemple d'appel

  {"name": "create_account", "arguments": {"email": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"api_key": "texte", "account_id": 1, "verification": "texte"}}

• create_schedule≈ 1302 tokens

  Create a recurring (or custom-date) schedule and materialize its upcoming occurrences. Best practice: call preview_schedule_occurrences with the same recurrence settings first and confirm the dates with the user. This tool returns the created schedule AND an inline preview of its next occurrences so you can show what was set up. You can optionally seed the roster with contact_ids at creation. Requires the `schedules:write` scope.

  Paramètres, retour & exemple (15)

  Paramètres

  • time · ? · optionnel
    Wall-clock time of day "HH:mm" (24-hour) in the account timezone, or null for no specific time.
  • notes · ? · optionnel
    Free-text internal notes, or null.
  • end_date · ? · optionnel
    "yyyy-MM-dd" (account timezone) after which occurrences stop, or null for no end date.
  • group_id · ? · optionnel
    Id of an existing volunteer group to attach, or null. Unknown ids are ignored.
  • job_name · string · requis
    The role/task volunteers are reminded about. Matched case-insensitively against the account's existing jobs and created if new.
  • start_date · ? · optionnel
    "yyyy-MM-dd" (account timezone) before which no occurrences materialize, or null for no lower bound. For 'biweekly' this also picks which week the 14-day rotation lands on; when omitted, the server uses the first selected weekday after today. Updating an existing biweekly schedule with null keeps its stored date.
  • contact_ids · array · optionnel
    Optional initial roster (volunteer contact ids) to assign at creation. Ids not owned by this account are silently dropped. To change a roster later, use assign_contacts_to_schedule.
  • description · string · requis
    Short label shown on the schedule list and in reminders, e.g. "Sunday greeters".
  • nth_weekday · string · optionnel · sunday | monday | tuesday | wednesday | thursday | friday | saturday
    The weekday that recurs, for schedule_type 'monthly_nth'/'bimonthly_nth'. Defaults to sunday for those types.
  • start_month · integer · optionnel
    Anchor month (1=January … 12=December) the every-other-month cadence steps from, for the 'bimonthly_*' types. Defaults to the account's current month.
  • custom_dates · array · optionnel
    Explicit list of "yyyy-MM-dd" dates. Required (non-empty) when schedule_type is 'custom'; ignored otherwise.
  • day_of_month · integer · optionnel
    Fixed day of the month for the 'fixed' types. Defaults to 1. Clamped to the last day of shorter months (e.g. 31 in February becomes the 28th/29th).
  • days_of_week · array · optionnel
    Weekday names this recurs on, e.g. ["tuesday","thursday"]. Required (non-empty) when schedule_type is 'weekly' or 'biweekly'; ignored otherwise.
  • schedule_type · string · requis · weekly | biweekly | monthly_fixed | monthly_nth | bimonthly_fixed | bimonthly_nth | custom
    Recurrence shape. 'weekly' recurs on one or more days of the week; 'biweekly' is the same weekday mask every 14 days (start_date picks which week; not BiMonthly, which is every other month); 'monthly_fixed'/'bimonthly_fixed' recur on a fixed day of the month; 'monthly_nth'/'bimonthly_nth' recur on the Nth weekday of the month; the 'bimonthly_*' variants also alternate months starting from start_month; 'custom' uses an explicit list of dates.
  • week_of_month · integer · optionnel
    Which occurrence of the weekday in the month (1st–5th), for the Nth-weekday types. Defaults to 1.

  Exemple d'appel

  {"name": "create_schedule", "arguments": {"job_name": "texte", "description": "texte", "schedule_type": "weekly"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"schedule": {}, "upcoming_occurrences": []}}

• get_account_overview≈ 450 tokens

  Read the current VolunteerReminder account: organization name, plan and entitlements, current reminder send mode, and volunteer usage vs the plan limit. Call this first to understand what the account can do before creating schedules or contacts. Note the `reminder_mode`: an account created through this connector (create_account) starts in `test` (reminders reroute to the owner, never to volunteers); only a human can switch it to `live` from the dashboard. `effective_mode` is what actually happens at send time.

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "get_account_overview", "arguments": {}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"plan": {}, "usage": {}, "account": {}, "reminder_mode": "test", "effective_mode": "off"}}

• get_open_days≈ 277 tokens

  List calendar days in the look-ahead window that have no attendable shift yet, plus recurring monthly slots not yet claimed by a schedule — i.e. where the account still needs volunteers. Requires the `read` scope.

  Paramètres, retour & exemple (2)

  Paramètres

  • months · integer · optionnel
    How many months to look ahead (1–24). Default 12.
  • current_year_only · boolean · optionnel
    When true (the default), clamp the window to the end of the current calendar year instead of crossing into next year.

  Exemple d'appel

  {"name": "get_open_days", "arguments": {"months": 1, "current_year_only": true}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"open_dates": [], "open_schedules": []}}

• get_pricing≈ 285 tokens

  Read VolunteerReminder's public plan catalog: each plan's monthly and annual price (USD), volunteer limit, and included features (SMS reminders are included with no per-message credits or metering). No API key required — use this to help a user comparison-shop or decide which plan fits before they sign up.

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "get_pricing", "arguments": {}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"plans": [], "product": "texte", "signup_url": "texte"}}

• get_reminder_settings≈ 270 tokens

  Read the account's reminder lead times (the account-wide default plus any per-job overrides) and which channels (email / SMS) are available on the current plan. Reminder overrides are per JOB, not per individual schedule. Requires the `read` scope.

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "get_reminder_settings", "arguments": {}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"channels": {}, "job_overrides": [], "global_default": "texte"}}

• get_schedule≈ 231 tokens

  Get one schedule's full configuration: recurrence settings, job/role, group, roster (contact ids), start/end dates, and notes. Requires the `read` scope.

  Paramètres, retour & exemple (1)

  Paramètres

  • schedule_id · integer · requis
    The schedule's numeric id (from list_schedules or get_schedule).

  Exemple d'appel

  {"name": "get_schedule", "arguments": {"schedule_id": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"id": 1, "description": "texte", "schedule_type": "texte"}}

• get_send_history≈ 252 tokens

  Read recent reminder outcomes — which reminders were sent and which failed — newest first, paginated. Use this to confirm reminders actually went out. Requires the `read` scope.

  Paramètres, retour & exemple (2)

  Paramètres

  • page · integer · optionnel
    1-indexed page number. Default 1.
  • per_page · integer · optionnel
    Rows per page (max 100). Default 20.

  Exemple d'appel

  {"name": "get_send_history", "arguments": {"page": 1, "per_page": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"total": 1, "entries": [], "has_more": true}}

• get_upcoming_shifts≈ 402 tokens

  Who is volunteering when. Lists upcoming shifts with date/time, schedule, whether that date is still on, and the rostered volunteers' names. Omit `schedule_id` to cover EVERY active schedule in one call (best for questions like "who is on this Sunday?": pass from and to as that same date). A bare "yyyy-MM-dd" `to` includes that whole day. Requires the `read` scope.

  Paramètres, retour & exemple (4)

  Paramètres

  • to · string · optionnel
    End of the range, same formats as `from`; a bare date includes that whole day. Defaults to 90 days from now.
  • from · string · optionnel
    Start of the range: "yyyy-MM-dd" (account timezone) or a full ISO 8601 datetime. Defaults to now.
  • limit · integer · optionnel
    Maximum shifts to return (default 20, max 100).
  • schedule_id · integer · optionnel
    Limit to one schedule (id from list_schedules). Omit to include all active schedules.

  Exemple d'appel

  {"name": "get_upcoming_shifts", "arguments": {"to": "texte", "from": "texte", "limit": 1, "schedule_id": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"occurrences": []}}

• import_volunteer_schedule≈ 889 tokens

  Parse a pasted or uploaded volunteer roster + schedule (CSV or a table with columns like name, phone, email, job/role, day, start, end) and either PREVIEW or CREATE the contacts, schedules, and assignments. Always call first with confirm=false and show the user the upcoming shifts; only call again with confirm=true, passing back preview_token from that preview, after they approve. Import is test-mode only and is refused on some accounts. Use create_account first if they do not have an account — do not invent a second signup path. This tool never changes reminder mode, never enables the confirm loop or substitute finder, and never texts real volunteers. New accounts stay in test mode. Requires `read` for preview; `schedules:write` and `contacts:write` to commit. Set consent_attested=true on commit when any row has a phone number (the coordinator affirms the volunteers agreed to be texted).

  Paramètres, retour & exemple (4)

  Paramètres

  • text · string · requis
    The roster as CSV, TSV, pipe-delimited text, or a headerless table in the order name, phone, email, job, day, start, end. Quoted CSV fields are fine. Do not log this text.
  • confirm · boolean · optionnel
    false (default) = parse and preview only, no writes. true = create the contacts, schedules, and assignments after the user approved the preview. confirm=true requires preview_token from the preceding preview.
  • preview_token · string · optionnel
    Required when confirm=true. Copy the preview_token returned by the preceding confirm=false call for this exact roster text.
  • consent_attested · boolean · optionnel
    Required true on confirm=true when any contact has a phone number. Affirms the volunteers agreed to receive shift-reminder texts.

  Exemple d'appel

  {"name": "import_volunteer_schedule", "arguments": {"text": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"ok": true, "errors": [], "warnings": [], "row_count": 1, "schedules": [], "contact_count": 1, "preview_token": "texte", "reminder_mode": "test", "schedule_count": 1, "contacts_created": 1, "schedules_created": 1, "skipped_row_count": 1}}

• list_contacts≈ 178 tokens

  List all volunteers on the account's roster, each with contact details and group. Requires the `read` scope.

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "list_contacts", "arguments": {}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"contacts": []}}

• list_schedules≈ 202 tokens

  List all active (non-archived) schedules on the account, each with its description, job/role (name and job_id), next upcoming occurrence, and how many volunteers are rostered. Requires the `read` scope.

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "list_schedules", "arguments": {}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"schedules": []}}

• preview_schedule_occurrences≈ 1022 tokens

  PURE and side-effect-free: computes the next occurrence dates a recurrence configuration WOULD produce, without creating anything. Use this to show the user the concrete dates (e.g. 'the next 8 Tuesdays at 9:00 AM Central') and get their confirmation BEFORE calling create_schedule. Requires the `read` scope.

  Paramètres, retour & exemple (11)

  Paramètres

  • time · ? · optionnel
    Wall-clock time of day "HH:mm" (24-hour) in the account timezone, or null for no specific time.
  • count · integer · optionnel
    How many upcoming occurrences to return (default 8, max 52).
  • end_date · ? · optionnel
    "yyyy-MM-dd" (account timezone) after which occurrences stop, or null for no end date.
  • start_date · ? · optionnel
    "yyyy-MM-dd" (account timezone) before which no occurrences materialize, or null for no lower bound. For 'biweekly' this also picks which week the 14-day rotation lands on; when omitted, the server uses the first selected weekday after today. Updating an existing biweekly schedule with null keeps its stored date.
  • nth_weekday · string · optionnel · sunday | monday | tuesday | wednesday | thursday | friday | saturday
    The weekday that recurs, for schedule_type 'monthly_nth'/'bimonthly_nth'. Defaults to sunday for those types.
  • start_month · integer · optionnel
    Anchor month (1=January … 12=December) the every-other-month cadence steps from, for the 'bimonthly_*' types. Defaults to the account's current month.
  • custom_dates · array · optionnel
    Explicit list of "yyyy-MM-dd" dates. Required (non-empty) when schedule_type is 'custom'; ignored otherwise.
  • day_of_month · integer · optionnel
    Fixed day of the month for the 'fixed' types. Defaults to 1. Clamped to the last day of shorter months (e.g. 31 in February becomes the 28th/29th).
  • days_of_week · array · optionnel
    Weekday names this recurs on, e.g. ["tuesday","thursday"]. Required (non-empty) when schedule_type is 'weekly' or 'biweekly'; ignored otherwise.
  • schedule_type · string · requis · weekly | biweekly | monthly_fixed | monthly_nth | bimonthly_fixed | bimonthly_nth | custom
    Recurrence shape. 'weekly' recurs on one or more days of the week; 'biweekly' is the same weekday mask every 14 days (start_date picks which week; not BiMonthly, which is every other month); 'monthly_fixed'/'bimonthly_fixed' recur on a fixed day of the month; 'monthly_nth'/'bimonthly_nth' recur on the Nth weekday of the month; the 'bimonthly_*' variants also alternate months starting from start_month; 'custom' uses an explicit list of dates.
  • week_of_month · integer · optionnel
    Which occurrence of the weekday in the month (1st–5th), for the Nth-weekday types. Defaults to 1.

  Exemple d'appel

  {"name": "preview_schedule_occurrences", "arguments": {"schedule_type": "weekly"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"time_zone": "texte", "occurrences": []}}

• remove_contact≈ 224 tokens

  Remove (soft-delete) a volunteer from the roster. This frees a volunteer-cap slot and removes them from any schedule rosters they were on. Confirm with the user before removing. Requires the `contacts:write` scope.

  Paramètres, retour & exemple (1)

  Paramètres

  • contact_id · integer · requis
    The contact's numeric id (from list_contacts).

  Exemple d'appel

  {"name": "remove_contact", "arguments": {"contact_id": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"id": 1, "deleted": true}}

• remove_reminder_rule≈ 205 tokens

  Remove a reminder lead-time rule. Provide `job_id` to remove that job's override; omit it to clear the account-wide default. Returns the updated reminder settings. Requires the `reminders:write` scope.

  Paramètres, retour & exemple (1)

  Paramètres

  • job_id · integer · optionnel
    Remove this job's lead-time override. Omit to clear the account-wide default.

  Exemple d'appel

  {"name": "remove_reminder_rule", "arguments": {"job_id": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• send_test_reminder≈ 306 tokens

  Send a single TEST reminder to the account owner's own email/phone so they can preview what a reminder looks like. This never reaches volunteers — it always reroutes to the owner. Optionally pass a schedule_id to preview that schedule's reminder; otherwise a generic sample is sent. It is a real message that cannot be unsent, so confirm with the user first. Requires the `reminders:write` scope.

  Paramètres, retour & exemple (1)

  Paramètres

  • schedule_id · integer · optionnel
    Preview the reminder for this schedule. Omit for a generic sample reminder.

  Exemple d'appel

  {"name": "send_test_reminder", "arguments": {"schedule_id": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"note": "texte", "sent": true, "channel": "texte", "schedule_id": "texte", "delivered_to": "texte"}}

• set_reminder_rule≈ 645 tokens

  Set the reminder lead time: the account-wide default and/or a per-job override. Provide at least one of `global_default` or `job_override`, and set at least one of days/hours/minutes greater than zero. Overrides are per JOB (a job may back several schedules); get the job_id from list_schedules. Replaces any earlier override for that job. Requires the `reminders:write` scope.

  Paramètres, retour & exemple (3)

  Paramètres

  • require_sms · boolean · optionnel
    Assert SMS should be used. If true and the plan does NOT include SMS, the whole request is rejected with a message that the plan does not include SMS (nothing is saved). Omit or set false to make no assertion.
  • job_override · object · optionnel
    Create or replace the lead-time override for one job.
  • global_default · object · optionnel
    Set (or replace) the account-wide default lead time.

  Exemple d'appel

  {"name": "set_reminder_rule", "arguments": {"require_sms": true, "job_override": {}, "global_default": {}}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• start_checkout≈ 321 tokens

  Get a Stripe-hosted Checkout URL for the account to subscribe to a paid plan, then HAND THE URL TO THE HUMAN to open and complete payment. You never take payment yourself and never see card details. Use get_pricing first to pick a plan. Fails if the account already has an active subscription (manage that from the billing dashboard). Requires a connected API key (any scope with `read`).

  Paramètres, retour & exemple (2)

  Paramètres

  • plan · string · requis · basic | deluxe | pro
    The plan id to subscribe to (see get_pricing).
  • interval · string · optionnel · monthly | annual
    Billing interval. Defaults to monthly.

  Exemple d'appel

  {"name": "start_checkout", "arguments": {"plan": "basic"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"plan": "texte", "interval": "monthly", "checkout_url": "texte"}}

• update_contact≈ 617 tokens

  Update a volunteer's details. Send only the fields you want to change; a field set to null clears it. Requires the `contacts:write` scope.

  Paramètres, retour & exemple (10)

  Paramètres

  • notes · ? · optionnel
    Free-text notes about the contact, or null.
  • group_id · ? · optionnel
    Id of an existing group on this account to file the contact under, or null.
  • full_name · string · optionnel
    New display name.
  • last_name · ? · optionnel
    Last name, or null.
  • contact_id · integer · requis
    The contact's numeric id (from list_contacts).
  • first_name · ? · optionnel
    First name, or null.
  • land_phone · ? · optionnel
    Landline number (informational only, never texted), or null.
  • mobile_phone · ? · optionnel
    Mobile number for SMS reminders. Accepts E.164 (+15125550100) or a plain 10-digit US/Canada number; stored as E.164. Send null to clear.
  • email_address · ? · optionnel
    Email address reminders may be sent to, or null.
  • consent_attested · boolean · optionnel
    Required true when setting or changing mobile_phone. Set it only after the user confirms these volunteers agreed to receive shift-reminder texts. Not needed for email-only volunteers.

  Exemple d'appel

  {"name": "update_contact", "arguments": {"contact_id": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"id": 1, "full_name": "texte"}}

• update_schedule≈ 1273 tokens

  Partially update a schedule — send only the fields you want to change; unset fields keep their current value. Changing recurrence fields recomputes and re-materializes future occurrences. If the change would remove upcoming shifts, nothing is saved and the tool returns confirm_remove_required with the `removed` dates and a `confirm_token`. Show the user those dates; only if they agree, call again with the same changes plus confirm_remove: true and that confirm_token. This tool does NOT change the roster; use assign_contacts_to_schedule for that. Requires the `schedules:write` scope.

  Paramètres, retour & exemple (17)

  Paramètres

  • time · ? · optionnel
    Wall-clock time of day "HH:mm" (24-hour) in the account timezone, or null for no specific time.
  • notes · ? · optionnel
    New notes, or null to clear.
  • end_date · ? · optionnel
    "yyyy-MM-dd" (account timezone) after which occurrences stop, or null for no end date.
  • group_id · ? · optionnel
    New group id, or null to detach. Unknown ids are ignored.
  • job_name · string · optionnel
    New job/role name.
  • start_date · ? · optionnel
    "yyyy-MM-dd" (account timezone) before which no occurrences materialize, or null for no lower bound. For 'biweekly' this also picks which week the 14-day rotation lands on; when omitted, the server uses the first selected weekday after today. Updating an existing biweekly schedule with null keeps its stored date.
  • description · string · optionnel
    New schedule label.
  • nth_weekday · string · optionnel · sunday | monday | tuesday | wednesday | thursday | friday | saturday
    The weekday that recurs, for schedule_type 'monthly_nth'/'bimonthly_nth'. Defaults to sunday for those types.
  • schedule_id · integer · requis
    The schedule's numeric id (from list_schedules or get_schedule).
  • start_month · integer · optionnel
    Anchor month (1=January … 12=December) the every-other-month cadence steps from, for the 'bimonthly_*' types. Defaults to the account's current month.
  • custom_dates · array · optionnel
    Explicit list of "yyyy-MM-dd" dates. Required (non-empty) when schedule_type is 'custom'; ignored otherwise.
  • day_of_month · integer · optionnel
    Fixed day of the month for the 'fixed' types. Defaults to 1. Clamped to the last day of shorter months (e.g. 31 in February becomes the 28th/29th).
  • days_of_week · array · optionnel
    Weekday names this recurs on, e.g. ["tuesday","thursday"]. Required (non-empty) when schedule_type is 'weekly' or 'biweekly'; ignored otherwise.
  • confirm_token · string · optionnel
    The confirm_token from the confirm_remove_required result for this same change.
  • schedule_type · string · optionnel · weekly | biweekly | monthly_fixed | monthly_nth | bimonthly_fixed | bimonthly_nth | custom
    Recurrence shape. 'weekly' recurs on one or more days of the week; 'biweekly' is the same weekday mask every 14 days (start_date picks which week; not BiMonthly, which is every other month); 'monthly_fixed'/'bimonthly_fixed' recur on a fixed day of the month; 'monthly_nth'/'bimonthly_nth' recur on the Nth weekday of the month; the 'bimonthly_*' variants also alternate months starting from start_month; 'custom' uses an explicit list of dates.
  • week_of_month · integer · optionnel
    Which occurrence of the weekday in the month (1st–5th), for the Nth-weekday types. Defaults to 1.
  • confirm_remove · boolean · optionnel
    Set true to apply a change that removes upcoming shifts, only after the user approved the dates a previous confirm_remove_required result listed. Requires confirm_token from that result.

  Exemple d'appel

  {"name": "update_schedule", "arguments": {"schedule_id": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"id": 1, "description": "texte"}}

C'est votre serveur ?

Revendiquez-le sur l'espace créateur (preuve GitHub, domaine ou npm) pour afficher le badge « propriétaire vérifié » et lancer un pentest comportemental à la demande afin d'obtenir le badge « Vérifié ».

Créer un compte / revendiquer →

Source

https://mcp.volunteerreminder.com/mcp