Skip to main content
Glama

Move a session to a new time or room (organizers only)

event_session_move
DestructiveIdempotent

Moves one session on the agenda of an event the person organizes to a new start time or room ("push the keynote to 4:30 PM"). It moves a named session on the agenda or schedule; what the pass itself shows, such as a doors-open time on the pass, is a pass setting, which changes quietly and can be undone. Pass holders are notified unless notify is false. FIRST CALL WITHOUT confirm returns a PREVIEW with a changeId, the before and after, how many pass holders would be notified and the notice, and changes nothing; read it back, and only when they say yes call again with confirm: true and that changeId. Name the session by sessionId or title; on AMBIGUOUS or NO_SUCH_SESSION read the candidates back and ask. Only the organizer of the event can change it; anybody else is refused, read out as given. It requires a personal connector token.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "eventIdOrName": "<eventIdOrName>"
    },
    "name": "event_session_move"
  }
}

Input Schema

NameRequiredDescriptionDefault
atNoOptional current start ("10:30 AM"), for sessions sharing a title.
endNoOptional new end; else it keeps its length.
dateNoOptional day, YYYY-MM-DD.
roomNoNew room or place label.
startNoNew start, "4:30 PM" or a timestamp, in the event's time zone.
notifyNoOptional; false keeps the move quiet.
confirmNoLeave out for the preview; after the organizer says yes, true with the changeId.
changeIdNoThe changeId the preview returned.
sessionIdNoThe session id as the agenda gave it.
sessionTitleNoOr the session title, when there is no sessionId.
eventIdOrNameYesThe event id or name as the organizer spells it.

Output Schema

NameRequiredDescriptionDefault
okNo
kindNo
errorNo
appliedNo
changesNo
messageNo
previewNo
sessionNo
changeIdNo
servedByNo
candidatesNo
lockScreenNo
passUpdateNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed11 schema fields changed
    • changedInput schema / properties / at / description
      Previous value: -"OPTIONAL. The session's current start (\"10:30 AM\"), which distinguishes sessions that share a title."New value: +"Optional current start (\"10:30 AM\"), for sessions sharing a title."
    • changedInput schema / properties / changeId / description
      Previous value: -"REQUIRED with confirm: the changeId the preview returned."New value: +"The changeId the preview returned."
    • changedInput schema / properties / confirm / description
      Previous value: -"Leave out for the PREVIEW. Only after the organizer says yes to the preview, call again with confirm: true and the changeId."New value: +"Leave out for the preview; after the organizer says yes, true with the changeId."
    • changedInput schema / properties / date / description
      Previous value: -"OPTIONAL. The day, YYYY-MM-DD, when the event runs more than one day or the session moves to another day."New value: +"Optional day, YYYY-MM-DD."
    • changedInput schema / properties / end / description
      Previous value: -"The new end, same forms. Left out, the session keeps its length."New value: +"Optional new end; else it keeps its length."
    • changedInput schema / properties / eventIdOrName / description
      Previous value: -"REQUIRED. The event id or the event name as the organizer spells it."New value: +"The event id or name as the organizer spells it."
    • changedInput schema / properties / notify / description
      Previous value: -"OPTIONAL. A move notifies pass holders by default; false keeps it quiet."New value: +"Optional; false keeps the move quiet."
    • changedInput schema / properties / room / description
      Previous value: -"The room or place label, plain words."New value: +"New room or place label."
    • changedInput schema / properties / sessionId / description
      Previous value: -"The session's id exactly as the agenda or a candidates list gave it."New value: +"The session id as the agenda gave it."
    • changedInput schema / properties / sessionTitle / description
      Previous value: -"Or the session's title as the agenda spells it, when there is no sessionId."New value: +"Or the session title, when there is no sessionId."
    • changedInput schema / properties / start / description
      Previous value: -"The new start: \"4:30 PM\", or a full timestamp with a time zone. Read in the event's own time zone."New value: +"New start, \"4:30 PM\" or a timestamp, in the event's time zone."
  2. Added

TDQS

A4.5/5.0
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Beyond the annotations it discloses the preview/commit split, that pass holders are notified unless `notify` is false, that non-organizers are refused, and that a personal connector token is required. The annotations already flag this as destructive and idempotent, and the description adds the preview guarantee that is genuinely new information. No conflict with the annotation profile.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The core action is front-loaded in the opening clause, followed by disambiguation and the preview/confirm protocol in priority order. It is dense and a few sentences carry stacked clauses and parentheticals, but each sentence contributes a distinct rule rather than restating the schema.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For an 11-parameter mutation tool with an output schema, the description covers the preview return shape, the notification side effect, the auth requirement, and the error/ambiguity paths. An agent has everything needed to run the two-step flow correctly without inspecting the output schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds workflow meaning the schema cannot: `confirm` and `changeId` are a paired preview/commit contract, and `notify: false` is framed as keeping the move quiet. It also explains why `at` exists (sessions sharing a title) and that `sessionId` and title are alternatives. The remaining parameter meaning is still carried by the schema itself.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The first sentence gives a specific verb and resource plus scope: "Moves one session on the agenda of an event the person organizes to a new start time or room." It further separates itself from a nearby concept ("what the pass itself shows, such as a doors-open time on the pass, is a pass setting"), which prevents confusion with pass-notice tools. It never names a concrete sibling tool such as a rename or cancel tool, so it stops short of full sibling differentiation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It states the exact invocation protocol: a first call without `confirm` returns a preview and changes nothing, then a second call with `confirm: true` and the returned `changeId` applies it. It also names the conditions and required behavior for ambiguity ("on AMBIGUOUS or NO_SUCH_SESSION read the candidates back and ask") and the authorization boundary (organizer only, everyone else refused).

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources