Sonar Connections

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. 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.

Input Schema

Name	Required	Description
`end`	No	The end, same forms.
`date`	No	Optional day, YYYY-MM-DD.
`room`	No	The room or place label, plain words.
`start`	No	Start, "4:30 PM" or a timestamp, in the event's time zone.
`title`	No	The new session's title.
`notify`	No	Optional; true notifies pass holders.
`confirm`	No	Leave out for the preview; after the organizer says yes, true with the changeId.
`changeId`	No	The changeId the preview returned.
`speakers`	No	Optional speaker names.
`eventIdOrName`	Yes	The event id or name as the organizer spells it.

Output Schema

Name	Required	Description	Default
`ok`	No
`kind`	No
`error`	No
`applied`	No
`changes`	No
`message`	No
`preview`	No
`session`	No
`changeId`	No
`servedBy`	No
`candidates`	No
`lockScreen`	No
`passUpdate`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed7 schema fields changedOct 16, 2026

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."

AddedOct 12, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations only say this is a non-read-only, non-destructive, non-idempotent write; the description goes well beyond them by disclosing the dry-run preview contract, that the first call changes nothing, the quiet-by-default notification behavior, and the authorization failure mode. That is exactly the extra context the annotations cannot carry.

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?

Front-loads the action and scope, then the confirmation protocol, then the authorization constraint. Dense but every sentence carries distinct information; some clauses are compressed to the point of terseness ('read out as given').

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 a 10-parameter mutation tool with an output schema, the description covers the workflow, the required permissions, the side-effect profile and the optional notification path. Return-value detail is correctly delegated to 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; the description adds real value by naming the core fields (title, start, end, room) versus the optional ones (date, speakers, notify) and by explaining the confirm/changeId pairing semantically rather than syntactically. It stops short of describing accepted time formats, which the schema already handles.

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?

States a specific verb and resource plus a scope qualifier ('Adds a new session to the agenda of an event the person organizes'), which cleanly separates it from event_session_move, event_session_rename and event_session_cancel.

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?

Prescribes the exact two-step workflow: first call without `confirm` returns a preview, and the second call requires `confirm: true` plus the returned `changeId` after the user agrees. It also states the preconditions (organizer-only, personal connector token), 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.

All Sonar Connections tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?