Sonar Connections

List booths and vendors

events_booths

Read-only

Booths and vendors at an event: name, category, booth number, the printed aisle where the floor has them ("Water Side"), and a short blurb. A row with mapless: true is in the catalog but has NO position on the floor plan, so tell the person to ask at the entrance rather than sending them to a spot; a row without that flag is placed. Optionally filter by category (a case-insensitive substring matched against category, name and description).

Input Schema

Name	Required	Description
`category`	No	Optional category filter, e.g. "dessert"
`boothNameOrId`	No	Optional booth id or name: returns that one booth's full card instead of the list
`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
`booth`	No
`count`	No
`error`	No
`found`	No
`booths`	No
`filter`	No
`eventId`	No
`message`	No
`eventName`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedOct 16, 2026

addedInput schema / properties / boothNameOrId

Added value: +{
+  "description": "Optional booth id or name: returns that one booth's full card instead of the list",
+  "type": "string"
+}

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

changedOutput schema / anyOf

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

addedOutput schema / properties / booth
```
Added value: +{
+  "type": "object"
+}
```

Changed1 schema field changedOct 11, 2026

changedOutput schema / (root)

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

First observedSep 21, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already cover the read-only, closed-world safety profile, so the description clears the lower bar and adds genuinely behavioral detail: the meaning of `mapless: true` (in catalog but no floor position) and how to handle it in conversation versus a placed row. It also discloses the filter's matching rule (case-insensitive substring across category, name and description). It does not say whether `category` filtering also applies in single-booth mode, which is a minor residual gap.

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?

Three sentences, front-loaded with the resource and its fields, then the mapless caveat, then the filter rule. Every sentence carries information, though the entrance-handling clause is slightly verbose for what is a presentation instruction.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/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 need not explain return values, yet it helpfully names the key fields and their semantics (printed aisle label, blurb, mapless flag). The one omission that matters is the single-booth mode triggered by `boothNameOrId`, which changes the result from a list to one full card and is only documented in the 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%, giving a baseline of 3, but the description earns an increment by specifying that the category filter is a case-insensitive substring matched against category, name and description — a materially broader matching rule than the schema's 'Optional category filter, e.g. "dessert"' suggests. It says nothing about `boothNameOrId`, which switches the response shape to a single full card; that behavior rests entirely on the schema.

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 opens with a specific verb+resource ('Booths and vendors at an event') and enumerates the returned fields, so an agent knows exactly what it gets. It does not name a sibling it is not (e.g. events_floor_card for a spatial rendering, events_speakers for the speaker list), so differentiation is left implicit rather than stated.

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 implied by the field list and by the instruction to 'tell the person to ask at the entrance' for mapless rows, which gives real presentation guidance. But there is no explicit when-to-use or when-not-to-use versus events_floor_card or events_speakers, and the description never mentions the single-booth lookup mode, so the agent has to infer the selection condition from the schema.

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?