Sonar Connections

Rename a session (organizers only)

event_session_rename

DestructiveIdempotent

Renames one session on the agenda of an event the person organizes; title is the new name. Quiet unless notify is true. 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.

Input Schema

Name	Required	Description
`at`	No	Optional current start ("10:30 AM"), for sessions sharing a title.
`title`	No	The session's new 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.
`sessionId`	No	The session id as the agenda gave it.
`sessionTitle`	No	Or the session title, when there is no sessionId.
`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 / 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 / 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 / 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."

AddedOct 12, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Goes well past the annotations: discloses the preview/confirm two-phase protocol, that the preview is non-mutating and reports who would be notified, that `notify` is quiet-by-default, and that only the event organizer may act and others are refused. Annotations (destructive, idempotent) are consistent with, not contradicted by, this text.

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-loaded with the core action and the preview requirement, and no sentence is filler. The semicolon-chained clauses make it dense and slightly run-on, but every clause carries operational information.

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 8-parameter mutation with auth constraints and a two-step protocol, this covers everything an agent needs: sequencing, authorization, ambiguity handling, and what the preview returns. An output schema exists and the description still summarizes the preview payload appropriately.

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 earns extra by explaining relationships the schema cannot express — `confirm`/`changeId` must come from a prior preview, `notify` controls pass-holder notifications, and `sessionId`/title are alternatives for the same identification job. It stops short of explaining `at`'s disambiguation role, which stays in the schema.

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 ('Renames one session on the agenda of an event') plus the scope constraint that the caller must be the organizer. Siblings like event_session_move, event_session_cancel and event_session_add are clearly different operations, so an agent can route without opening a 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 procedure: first call without `confirm` to get a preview, read it back, and only re-call with `confirm: true` plus that `changeId` once the user agrees. It also names the ambiguity/not-found paths ('on AMBIGUOUS or NO_SUCH_SESSION read the candidates back and ask') rather than leaving error handling 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?