Sonar Connections

List an event's speakers

events_speakers

Read-only

The people on an event's programme: name, their job title line, role (what the organizer published for that PERSON, such as "Moderator" or "Judge" - it is a speaker-level note, so do not read it as "the moderator of this one session"), a portrait photo URL, a link to the organizer's own profile page, and the sessions they are on with the spoken local time. Ordered by when they are first on stage. Optionally filter to one day. Any field except the name may be null, which means the organizer published nothing there: say nothing rather than filling the gap. When an event publishes no speaker records the roster is built from the programme itself and source says "program"; those rows carry a kind of "speaker" or "performer" and nothing else about the person.

Input Schema

Name	Required	Description
`day`	No	Optional day filter: "today" or YYYY-MM-DD, read in the event's own timezone
`speaker`	No	Optional speaker name or speakerId: returns that one person's full record instead of the roster
`eventIdOrSlug`	Yes	Event id, public slug, or the event name as events_list spells it; short forms such as "the stroll" work.

Output Schema

Name	Required	Description	Default
`day`	No
`count`	No
`error`	No
`found`	No
`roster`	No
`source`	No
`eventId`	No
`message`	No
`speaker`	No
`timezone`	No
`eventName`	No
`eventDayCount`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedOct 16, 2026

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

addedInput schema / properties / speaker

Added value: +{
+  "description": "Optional speaker name or speakerId: returns that one person's full record instead of the roster",
+  "type": "string"
+}

changedOutput schema / anyOf

Previous value: -[
-  {
-    "required": [
-      "found",
-      "eventId",
-      "count",
-      "roster"
-    ]
-  },
-  {
-    "properties": {
-      "ok": {
-        "const": false
-      }
-    },
-    "required": [
-      "ok"
-    ]
-  },
-  {
-    "properties": {
-      "found": {
-        "const": false
-      }
-    },
-    "required": [
-      "found"
-    ]
-  },
-  {
-    "required": [
-      "error"
-    ]
-  }
-]New value: +[
+  {
+    "required": [
+      "found",
+      "eventId",
+      "count",
+      "roster"
+    ]
+  },
+  {
+    "required": [
+      "found",
+      "eventId",
+      "speaker"
+    ]
+  },
+  {
+    "properties": {
+      "ok": {
+        "const": false
+      }
+    },
+    "required": [
+      "ok"
+    ]
+  },
+  {
+    "properties": {
+      "found": {
+        "const": false
+      }
+    },
+    "required": [
+      "found"
+    ]
+  },
+  {
+    "required": [
+      "error"
+    ]
+  }
+]

addedOutput schema / properties / eventDayCount
```
Added value: +{
+  "type": "integer"
+}
```
addedOutput schema / properties / speaker
```
Added value: +{
+  "type": "object"
+}
```

Changed1 schema field changedOct 11, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "anyOf": [
+    {
+      "required": [
+        "found",
+        "eventId",
+        "count",
+        "roster"
+      ]
+    },
+    {
+      "properties": {
+        "ok": {
+          "const": false
+        }
+      },
+      "required": [
+        "ok"
+      ]
+    },
+    {
+      "properties": {
+        "found": {
+          "const": false
+        }
+      },
+      "required": [
+        "found"
+      ]
+    },
+    {
+      "required": [
+        "error"
+      ]
+    }
+  ],
+  "properties": {
+    "count": {
+      "type": "integer"
+    },
+    "day": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "error": {
+      "type": "string"
+    },
+    "eventId": {
+      "type": "string"
+    },
+    "eventName": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "found": {
+      "type": "boolean"
+    },
+    "message": {
+      "type": "string"
+    },
+    "roster": {
+      "items": {
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "source": {
+      "type": "string"
+    },
+    "timezone": {
+      "type": [
+        "string",
+        "null"
+      ]
+    }
+  },
+  "type": "object"
+}

First observedSep 21, 2026

TDQS

A4/5.0

Behavior5/5

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

Annotations only declare it is a safe, closed-world read; the description goes well beyond that with ordering (first on stage), null semantics ('say nothing rather than filling the gap'), and the fallback roster mode where `source` is 'program' and rows carry only a `kind`. These are non-obvious behaviors an agent cannot infer from structured fields, and they directly change how results should be presented.

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 resource and its fields, then the ordering, filter, null rule, and fallback mode in a logical sequence. It is a dense single paragraph and the long parenthetical about `role` is wordier than needed, but nearly every clause carries decision-relevant 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?

With an output schema present, the description does not need to explain return values, yet it still covers the two things the schema cannot: null handling and the degraded 'program'-sourced roster. An agent has everything needed to call the tool and to report its results faithfully.

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 all three parameters are already documented, making 3 the baseline. The description adds only that the day filter is optional and that times are spoken in local time; the `speaker` single-person mode and the flexible eventIdOrSlug forms are left to the schema. The detailed `role` discussion concerns a response field, not a parameter.

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?

The description states precisely what the resource is (the people on an event's programme) and enumerates the exact fields returned (name, job title line, role, photo, profile page, sessions with local time). An agent can tell this is a speaker-roster tool and not a schedule or event-detail tool. It never names a sibling or explicitly scopes itself against events_whats_on or events_get, so it stops short of a 5.

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

Usage Guidelines3/5

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

Usage is only implied: 'Optionally filter to one day' describes a filter but not when to reach for this tool instead of the schedule or overview tools, and the `speaker` parameter's single-person mode is left entirely to the schema. What guidance exists is interpretive (read `role` as a person-level note, not a session role), which helps post-call reasoning more than tool selection.

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?