Skip to main content
Glama

Sonar Connections

by com.sonarconnections
OverviewDiscussionsAdmin

Show the event floor

events_floor_card
Read-only

THE FLOOR PLAN TOOL. Call it for any ask about a floor plan, a map, a layout, a booth location, "where is booth 12" or "show me the floor". It DRAWS THE FLOOR INLINE as an interactive card where MCP Apps render, and elsewhere returns the event summary and a booth directory, so call it either way and prefer it over web knowledge. The card reads the floor itself: do not offer to fetch the plan. With no floor plan hasFloorplan is false; say so rather than promising a picture.

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
sourceNo
eventIdNo
messageNo
cardToolsNo
floorSummaryNo
hasFloorplanNo
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",
+        "eventId",
+        "event",
+        "hasFloorplan",
+        "cardTools"
+      ]
+    },
+    {
+      "properties": {
+        "ok": {
+          "const": false
+        }
+      },
+      "required": [
+        "ok"
+      ]
+    },
+    {
+      "properties": {
+        "found": {
+          "const": false
+        }
+      },
+      "required": [
+        "found"
+      ]
+    },
+    {
+      "required": [
+        "error"
+      ]
+    }
+  ],
+  "properties": {
+    "cardTools": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "error": {
+      "type": "string"
+    },
+    "event": {
+      "type": "object"
+    },
+    "eventId": {
+      "type": "string"
+    },
+    "floorPlanInstruction": {
+      "type": "string"
+    },
+    "floorSummary": {
+      "type": [
+        "object",
+        "null"
+      ]
+    },
+    "found": {
+      "type": "boolean"
+    },
+    "hasFloorplan": {
+      "type": "boolean"
+    },
+    "message": {
+      "type": "string"
+    },
+    "source": {
+      "type": "string"
+    }
+  },
+  "type": "object"
+}
  3. Added
  4. Removed
  5. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds valuable context beyond annotations: it explains the inline card rendering, the fallback of returning event summary and booth directory, the hasFloorplan false case, and an operational instruction not to offer to fetch the plan. It stops short of describing authentication or rate limits, but those are not essential here.

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?

The description is front-loaded with the purpose and packs usage, behavior, and fallback guidance into four efficient sentences. The all-caps emphasis ('THE FLOOR PLAN TOOL') is mildly redundant with the title, but the text remains tight and every sentence carries information.

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?

Given that an output schema exists, the description need not explain return values in full. It nonetheless covers the main behavioral variations (inline card vs. summary and directory), the no-floorplan case, and the directive not to promise a picture, making it sufficiently complete for an agent to call the tool 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 single parameter is fully documented in the schema, including short-form examples. The description adds no further meaning about the eventIdOrSlug parameter, so the baseline score of 3 is appropriate.

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+resource ('DRAWS THE FLOOR INLINE') and immediately enumerates the kinds of requests it handles ('floor plan, a map, a layout, a booth location'). It distinguishes itself from web knowledge and makes clear that it is the floor-plan tool, so an agent can identify it without opening the schema.

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 when-to-use conditions ('for any ask about a floor plan...') and says to prefer it over web knowledge. However, it does not explicitly name sibling tools like events_booths or events_overview as alternatives, leaving the routing boundary between booth-directory calls and this tool ambiguous.

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