Skip to main content
Glama

Add a session (organizers only)

event_session_add

Adds a new session to the agenda of an event the person organizes: title, start, end, room, optionally date and speakers. It adds a session to the agenda or schedule; a time or note on the pass itself is a pass setting, which changes what the pass shows, quietly, and can be undone. Quiet unless notify is true. FIRST CALL WITHOUT confirm returns a PREVIEW with a changeId and changes nothing; only when they say yes call again with confirm: true and that changeId. 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_add"
  }
}

Input Schema

NameRequiredDescriptionDefault
endNoThe end, same forms.
dateNoOptional day, YYYY-MM-DD.
roomNoThe room or place label, plain words.
startNoStart, "4:30 PM" or a timestamp, in the event's time zone.
titleNoThe new session's title.
notifyNoOptional; true notifies pass holders.
confirmNoLeave out for the preview; after the organizer says yes, true with the changeId.
changeIdNoThe changeId the preview returned.
speakersNoOptional speaker names.
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. Changed7 schema fields changed
    • 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."New value: +"Optional day, YYYY-MM-DD."
    • 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. Quiet by default; true notifies pass holders of the change."New value: +"Optional; true notifies pass holders."
    • changedInput schema / properties / speakers / description
      Previous value: -"OPTIONAL. Speaker names; a name that matches the event's speakers is linked, any other is kept as a plain name."New value: +"Optional speaker names."
    • changedInput schema / properties / start / description
      Previous value: -"The start: \"4:30 PM\", or a full timestamp with a time zone. Read in the event's own time zone."New value: +"Start, \"4:30 PM\" or a timestamp, in the event's time zone."
  2. Added

TDQS

A4.2/5.0
Behavior4/5

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

Goes well beyond the annotations by disclosing the two-phase preview/commit flow, the fact that the first call changes nothing, the `notify` side effect on pass holders, and the organizer-only authorization with refusal behavior. The only weak spot is the muddled clause 'quietly, and can be undone,' which describes the contrasted pass setting but reads ambiguously next to a non-idempotent, non-destructive mutation.

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

Conciseness3/5

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

Purpose and authorization are front-loaded and no sentence is pure filler, but the pass-setting contrast sentence is run-on and its trailing 'quietly, and can be undone' is hard to attach to the right subject. Phrases like 'read out as given' are opaque enough to cost a clarifying read.

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

Completeness4/5

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

Given an output schema exists, the description needn't detail return values, and it still names the `changeId` the preview yields. It covers auth, required token, side effects, and the commit path; it stops short of stating prerequisites such as whether the event must be published or how speaker conflicts are handled.

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

Parameters3/5

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

Schema coverage is 100%, so every parameter is already documented, including `confirm` and `changeId`. The description largely restates the schema's field list and the confirm workflow rather than adding new per-parameter meaning, so the baseline of 3 applies.

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

Purpose5/5

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

Opens with a specific verb, resource, and scope: 'Adds a new session to the agenda of an event the person organizes,' and immediately lists the fields involved. It also distinguishes itself from the adjacent concept of a pass setting, so an agent can separate this from pass-related siblings without opening the schema.

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?

Gives an explicit when-not: 'a time or note on the pass itself is a pass setting' rather than a session. It also spells out the required call sequence (preview first without `confirm`, then `confirm: true` with the returned `changeId` only after the organizer agrees), leaving nothing to inference.

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