Skip to main content
Glama

Sonar Connections

by com.sonarconnections
OverviewDiscussionsAdmin

Mark a booth away

booth_set_away
Idempotent

Marks a booth the person staffs as stepped away, or back; attendees looking at that booth see the presence change. Needs a personal connector token (a shared token reads but changes nothing), eventId, boothId and away. Only a booth the person owns, administers or staffs at that event can be changed, checked against live records on every call. It works in two steps: a call without confirm returns a preview of exactly what will change, plus a confirmToken, and changes nothing; a call with confirm true and that token makes the change. The token lasts two minutes, works once, and stops working if any argument changes.

Input Schema

NameRequiredDescriptionDefault
awayYestrue to mark the booth stepped away, false to mark it back.
boothIdYesThe booth id, exactly as events_booths returned it. Not the booth name.
confirmNoAbsent on the first call, which changes nothing. true, together with confirmToken, makes the change.
eventIdYesThe event the booth is at, exactly as events_list returned it.
requestIdNoAn id for this change chosen by the caller, at least 8 characters. A repeat with the same id and the same arguments returns the first result without changing anything a second time.
confirmTokenNoThe token the first call returned. Needed when confirm is true.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / confirm / description
      Previous value: -"Leave this out on the first call. Pass true with confirmToken to commit."New value: +"Absent on the first call, which changes nothing. true, together with confirmToken, makes the change."
    • changedInput schema / properties / confirmToken / description
      Previous value: -"The token the preview returned. Required when confirm is true."New value: +"The token the first call returned. Needed when confirm is true."
    • changedInput schema / properties / requestId / description
      Previous value: -"Your own id for this change, at least 8 characters. Sending the same one twice with the same arguments returns the first result instead of changing anything a second time."New value: +"An id for this change chosen by the caller, at least 8 characters. A repeat with the same id and the same arguments returns the first result without changing anything a second time."
  2. Added

TDQS

A4.6/5.0
Behavior5/5

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

Well beyond the annotations, the description discloses the two-step preview/confirm protocol, that the first call 'changes nothing', the confirmToken TTL of two minutes, single-use semantics, and that the token is invalidated if 'any argument changes'. It also explains permission checks against live records. This is exactly the behavioral context annotations alone cannot convey.

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?

It is front-loaded with purpose and effect, then requirements, then the two-step flow. The single dense paragraph packs a lot without wasteful sentences, though splitting the confirm flow into its own sentence or two would improve scannability.

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 mutation tool with no output schema, it covers everything an agent needs: auth requirements, authorization rules, the preview-then-confirm flow, what the preview returns (a description of changes plus confirmToken), token expiry, and idempotency expectations. Nothing material is missing.

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 baseline is 3, but the description adds real semantics: confirmToken's lifecycle (returned by preview, expires in two minutes, works once, invalidated by argument changes) and the shared-token caveat. It complements rather than repeats the schema's per-parameter docs.

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?

The description opens with a specific verb plus resource and effect: 'Marks a booth the person staffs as stepped away, or back; attendees looking at that booth see the presence change.' This distinguishes it from sibling booth tools (booth_claim_swag, booth_connect, booth_take_invite) which are about attendee actions, not staff presence on a booth.

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

Usage Guidelines4/5

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

It gives clear preconditions: a personal connector token is required because 'a shared token reads but changes nothing', and only booths the person owns, administers or staffs can be changed, 'checked against live records on every call'. It stops short of naming a sibling as an alternative for related operations, but the eligibility constraint is explicit enough to route an agent correctly.

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

All Sonar Connections toolsInspect
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