Skip to main content
Glama

Sonar Connections

by com.sonarconnections
OverviewDiscussionsAdmin

Get one Sonar Connections event

events_get
Read-only

Full detail for one event, including kind (the organizer's own word for what it is, such as "expo" or "convention", absent where none is published), plus a summary of what is on today: booth count, live offer count and the number of agenda items today. Accepts the event id or its public slug. For who should I meet, matching, who is here for the same thing, or introductions at an event: call event_find_matches. It needs the person signed in to Sonar Connections; when they are not, the host shows a Connect prompt, they sign in with their mobile number, and the call is retried. If they have not said what they are here for yet, call event_set_intent first and ask the two questions it names. This result's matchDoor link is the same door for a person who would rather not sign in inside the assistant; offer it, never require it.

Input Schema

NameRequiredDescriptionDefault
eventIdOrSlugYesEvent id, public slug, or the event name as events_list spells it; short forms such as "the stroll" work.

Output Schema

NameRequiredDescriptionDefault
errorNo
eventNo
foundNo
messageNo
todaysSummaryNo
floorPlanInstructionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / eventIdOrSlug / description
      Previous value: -"Event id (belmont_stroll), public slug (cba26), or the event NAME as events_list spells it (\"Summer Stroll & Savor\"). Common short forms work too (\"the stroll\", \"tie summit\")."New value: +"Event id, public slug, or the event name as events_list spells it; short forms such as \"the stroll\" work."
  2. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "anyOf": [
+    {
+      "required": [
+        "found",
+        "event",
+        "todaysSummary"
+      ]
+    },
+    {
+      "properties": {
+        "ok": {
+          "const": false
+        }
+      },
+      "required": [
+        "ok"
+      ]
+    },
+    {
+      "properties": {
+        "found": {
+          "const": false
+        }
+      },
+      "required": [
+        "found"
+      ]
+    },
+    {
+      "required": [
+        "error"
+      ]
+    }
+  ],
+  "properties": {
+    "error": {
+      "type": "string"
+    },
+    "event": {
+      "type": "object"
+    },
+    "floorPlanInstruction": {
+      "type": "string"
+    },
+    "found": {
+      "type": "boolean"
+    },
+    "message": {
+      "type": "string"
+    },
+    "todaysSummary": {
+      "type": "object"
+    }
+  },
+  "type": "object"
+}
  3. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Goes well beyond the readOnly/non-destructive annotations: discloses the auth requirement (person must be signed in), the Connect-prompt/mobile-number sign-in flow, that the call is retried afterward, and an alternate matchDoor door for people who don't want to sign in. Minor deduction because it doesn't say what happens if the event id/slug is not found.

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 purpose and return contents, then prerequisites and alternatives. It is a dense single paragraph with long compound sentences, and the trailing matchDoor sentence sits somewhat apart from the main call decision, but no sentence is disposable.

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?

Output schema exists so return shape needn't be described, yet the description still previews the payload fields. For a single-parameter read tool it covers purpose, prerequisites, auth flow, alternatives, and the no-sign-in fallback — everything needed to invoke correctly.

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 description coverage is 100% and the schema itself already documents eventIdOrSlug including the relaxed 'short forms such as "the stroll"' behavior, so the description's 'Accepts the event id or its public slug' adds nothing new. Baseline 3 applies; the schema carries the parameter burden.

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?

States a specific verb and resource: 'Full detail for one event', and enumerates what that detail contains (kind, booth count, live offer count, agenda items today). It implicitly separates itself from list/overview siblings by emphasizing single-event depth, though it never names events_list or events_overview as the alternatives it replaces.

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?

Explicitly routes away to `event_find_matches` for matching/introductions, and gives a prerequisite ordering rule: 'If they have not said what they are here for yet, call event_set_intent first'. It also states the fallback condition (matchDoor link) and that it must be offered, never required — clear when/when-not guidance.

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