io.usefulapi/schedule-it

None of its 15 tools are described as changing anything. For 15 the reading was uncertain, so no mark is shown.

• scheduleit_list_events

  “List scheduled events and tasks (bookings, shifts, jobs).”

  Publisher declares: read-only yes · destructive no · open-world yes

  12 inputs

  • fieldsstring“Comma-separated fields to return, e.g.”
  • date_fromstring“Events from this date (date_range_from).”
  • date_tostring“Events up to this date (date_range_to).”
  • titlestring“Events whose title contains this text.”
  • resource_idsarray“Only events linked to these resources (see resource_match).”
  • resource_matchstring“With resource_ids: any = linked to at least one (default), all = linked to every one, none = linked to none of them.”
  • event_idsarray“Only these event ids.”
  • tasks_onlyboolean“true = only tasks, false = only events that are not tasks.”
  • no_date_onlyboolean“true = only events with no date, false = only dated ones.”
  • modified_afterstring“Only events added or changed after this date (yyyy-mm-dd) or date and time (yyyy-mm-dd hh:mm).”
  • workspace_idinteger“Workspace id (Account Settings > Workspaces).”
  • limitinteger“Most events to return, 1-1000 (default 100).”
• scheduleit_get_event

  “One event or task by id with ALL its fields (title, dates, linked resources, notes, completion, priority, custom fields).”

  Publisher declares: read-only yes · destructive no · open-world yes

  1 input, 1 required

  • event_idintegerrequired“Schedule It event id.”
• scheduleit_create_event

  “WRITE: create a new event (booking, shift, job or task) in the Schedule It account, optionally linked to resources.”

  Publisher declares: read-only no · destructive no · idempotent no · open-world yes

  10 inputs, 1 required

  • titlestringrequired“Event title.”
  • resource_idsarray“Resources (people, rooms, equipment) the event is linked to (the `owner` field).”
  • date_startstring“Start, yyyy-mm-dd hh:mm[:ss].”
  • date_endstring“End, yyyy-mm-dd hh:mm[:ss].”
  • notesstring“Notes.”
  • custom_fieldsobject“Custom field values keyed custom1..custom9 (the account's custom field labels are set in Schedule It).”
  • completedinteger“Percent completed, 0-100.”
  • priorityinteger“Priority number (Schedule It's priority scale).”
  • color_backstring“Background colour, e.g.”
  • color_textstring“Text colour, e.g.”
• scheduleit_update_event

  “WRITE: change fields of an existing event; only the fields you pass are changed, the rest stay as they are.”

  Publisher declares: read-only no · destructive yes · idempotent yes · open-world yes

  11 inputs, 1 required

  • event_idintegerrequired“Schedule It event id.”
  • titlestring“Event title.”
  • resource_idsarray“Resources (people, rooms, equipment) the event is linked to (the `owner` field).”
  • date_startstring“Start, yyyy-mm-dd hh:mm[:ss].”
  • date_endstring“End, yyyy-mm-dd hh:mm[:ss].”
  • notesstring“Notes.”
  • custom_fieldsobject“Custom field values keyed custom1..custom9 (the account's custom field labels are set in Schedule It).”
  • completedinteger“Percent completed, 0-100.”
  • priorityinteger“Priority number (Schedule It's priority scale).”
  • color_backstring“Background colour, e.g.”
  • color_textstring“Text colour, e.g.”
• scheduleit_delete_event

  “WRITE, DESTRUCTIVE: permanently delete one event or task.”

  Publisher declares: read-only no · destructive yes · idempotent yes · open-world yes

  2 inputs, 2 required

  • event_idintegerrequired“Schedule It event id to delete.”
  • confirmbooleanrequired“Must be true: the user confirmed this event should be permanently deleted.”
• scheduleit_list_resources

  “List resources: the people, rooms, equipment or vehicles that events are scheduled against.”

  Publisher declares: read-only yes · destructive no · open-world yes

  7 inputs

  • fieldsstring“Comma-separated fields to return, e.g.”
  • namestring“Resources whose name contains this text.”
  • group_idsarray“Only resources in these groups.”
  • resource_idsarray“Only these resource ids.”
  • modified_afterstring“Only resources added or changed after this date (yyyy-mm-dd) or date and time (yyyy-mm-dd hh:mm).”
  • workspace_idinteger“Workspace id (Account Settings > Workspaces).”
  • limitinteger“Most resources to return, 1-1000 (default 100).”
• scheduleit_get_resource

  “One resource by id with ALL its fields (name, email, groups, details 1-10, colours, skills).”

  Publisher declares: read-only yes · destructive no · open-world yes

  1 input, 1 required

  • resource_idintegerrequired“Schedule It resource id.”
• scheduleit_create_resource

  “WRITE: add a new resource (a person, room, piece of equipment) to the Schedule It account.”

  Publisher declares: read-only no · destructive no · idempotent no · open-world yes

  7 inputs, 1 required

  • namestringrequired“Resource name.”
  • group_idsarray“Groups the resource belongs to (the `owner` field).”
  • emailstring“Email address of the resource (an empty string clears it on update).”
  • detailsobject“Detail values keyed data1..data10 (for example data1 = job title; the labels are set in Schedule It).”
  • color_backstring“Resource background colour, e.g.”
  • color_textstring“Resource text colour.”
  • color_event_backstring“Background colour of this resource's events.”
• scheduleit_update_resource

  “WRITE: change fields of an existing resource; only the fields you pass are changed.”

  Publisher declares: read-only no · destructive yes · idempotent yes · open-world yes

  8 inputs, 1 required

  • resource_idintegerrequired“Schedule It resource id.”
  • namestring“Resource name.”
  • group_idsarray“Groups the resource belongs to (the `owner` field).”
  • emailstring“Email address of the resource (an empty string clears it on update).”
  • detailsobject“Detail values keyed data1..data10 (for example data1 = job title; the labels are set in Schedule It).”
  • color_backstring“Resource background colour, e.g.”
  • color_textstring“Resource text colour.”
  • color_event_backstring“Background colour of this resource's events.”
• scheduleit_list_groups

  “List resource groups (the categories resources are organised in, e.g.”

  Publisher declares: read-only yes · destructive no · open-world yes

  5 inputs

  • fieldsstring“Comma-separated fields to return, e.g.”
  • namestring“Groups whose name contains this text.”
  • group_idsarray“Only these group ids.”
  • workspace_idinteger“Workspace id (Account Settings > Workspaces).”
  • limitinteger“Most groups to return, 1-1000 (default 100).”
• scheduleit_get_group

  “One resource group by id with ALL its fields.”

  Publisher declares: read-only yes · destructive no · open-world yes

  1 input, 1 required

  • group_idintegerrequired“Schedule It group id.”
• scheduleit_create_group

  “WRITE: add a new resource group to the Schedule It account.”

  Publisher declares: read-only no · destructive no · idempotent no · open-world yes

  7 inputs, 1 required

  • namestringrequired“Group name.”
  • color_backstring“Group colour, e.g.”
  • positioninteger“Position of the group in the schedule (positionv).”
  • min_resourcesinteger“Fewest resources an event needs from this group (0 = no minimum).”
  • max_resourcesinteger“Most resources an event can use from this group (0 = no limit).”
  • hide_from_mainboolean“Hide the group from the main schedule view.”
  • hide_from_eventboolean“Hide the group from the event form.”

Each quoted sentence is the first sentence of the publisher’s own description. The kind of tool and the “changes data” mark are our AI model’s reading of that description, not something we tested: two differently worded runs had to agree, otherwise no label is shown, and nobody has checked them by hand. A tool without the “changes data” mark is described as only reading, searching or calculating, or the two runs did not agree. No tool was called. Read the publisher’s full description before relying on it. “Publisher declares” lists the hints the server itself sends with the tool (MCP annotations: read-only, destructive, idempotent, open-world); they are the publisher's claims, not checked by us. Inputs are the parameters in the tool's own input schema: name, declared type, whether it is required, and the first sentence of its description. Read 2026-10-24.

The registry verifies a package once, when it is published, and does not re-check it. A difference below is about the listing, not a judgement of the publisher.