Skip to main content
Glama

events

by xyz.urbanplayground

Get Preference Onboarding

get_preference_onboarding
Read-only

Use this when a user wants consent-first questions before saving event preferences.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
profile_idNo

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed2 schema fields changed
    • removedInput schema / properties / profile_id / description
      Removed value: -"Stable user/profile id if already known."
    • changedOutput schema / (root)
      Previous value: -{
-  "anyOf": [
-    {
-      "properties": {
-        "assistant_instruction": {
-          "type": "string"
-        },
-        "consent_required": {
-          "type": "boolean"
-        },
-        "profile_id": {
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "questions": {
-          "items": {
-            "type": "string"
-          },
-          "type": "array"
-        }
-      },
-      "required": [
-        "consent_required",
-        "questions",
-        "assistant_instruction"
-      ],
-      "type": "object"
-    },
-    {
-      "properties": {
-        "assistant_instruction": {
-          "type": "string"
-        },
-        "cause": {
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "classification": {
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "code": {
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "error": {
-          "type": "string"
-        },
-        "hostname": {
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "retryable": {
-          "type": "boolean"
-        },
-        "status": {
-          "type": [
-            "number",
-            "null"
-          ]
-        },
-        "type": {
-          "type": "string"
-        },
-        "url": {
-          "type": [
-            "string",
-            "null"
-          ]
-        }
-      },
-      "required": [
-        "error"
-      ],
-      "type": "object"
-    }
-  ],
-  "type": "object"
-}New value: +null
  2. Changed2 schema fields changed
    • addedInput schema / properties / profile_id / description
      Added value: +"Stable user/profile id if already known."
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "anyOf": [
+    {
+      "properties": {
+        "assistant_instruction": {
+          "type": "string"
+        },
+        "consent_required": {
+          "type": "boolean"
+        },
+        "profile_id": {
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "questions": {
+          "items": {
+            "type": "string"
+          },
+          "type": "array"
+        }
+      },
+      "required": [
+        "consent_required",
+        "questions",
+        "assistant_instruction"
+      ],
+      "type": "object"
+    },
+    {
+      "properties": {
+        "assistant_instruction": {
+          "type": "string"
+        },
+        "cause": {
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "classification": {
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "code": {
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "error": {
+          "type": "string"
+        },
+        "hostname": {
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "retryable": {
+          "type": "boolean"
+        },
+        "status": {
+          "type": [
+            "number",
+            "null"
+          ]
+        },
+        "type": {
+          "type": "string"
+        },
+        "url": {
+          "type": [
+            "string",
+            "null"
+          ]
+        }
+      },
+      "required": [
+        "error"
+      ],
+      "type": "object"
+    }
+  ],
+  "type": "object"
+}
  3. Changed2 schema fields changed
    • removedInput schema / properties / profile_id / description
      Removed value: -"Stable user/profile id if already known."
    • changedOutput schema / (root)
      Previous value: -{
-  "anyOf": [
-    {
-      "properties": {
-        "assistant_instruction": {
-          "type": "string"
-        },
-        "consent_required": {
-          "type": "boolean"
-        },
-        "profile_id": {
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "questions": {
-          "items": {
-            "type": "string"
-          },
-          "type": "array"
-        }
-      },
-      "required": [
-        "consent_required",
-        "questions",
-        "assistant_instruction"
-      ],
-      "type": "object"
-    },
-    {
-      "properties": {
-        "assistant_instruction": {
-          "type": "string"
-        },
-        "cause": {
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "classification": {
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "code": {
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "error": {
-          "type": "string"
-        },
-        "hostname": {
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "retryable": {
-          "type": "boolean"
-        },
-        "status": {
-          "type": [
-            "number",
-            "null"
-          ]
-        },
-        "type": {
-          "type": "string"
-        },
-        "url": {
-          "type": [
-            "string",
-            "null"
-          ]
-        }
-      },
-      "required": [
-        "error"
-      ],
-      "type": "object"
-    }
-  ],
-  "type": "object"
-}New value: +null
  4. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, so the safe read-only nature is covered. The description adds context that this is a consent-first pre-save step, but it doesn't describe what the tool returns or how the onboarding questions behave.

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 a single concise sentence with no filler. It is easy to scan, though it could more directly state the tool's output.

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

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple tool with one optional parameter and no output schema, the description gives enough context to understand the general purpose. However, it lacks explicit information about the return value and the role of profile_id, leaving some ambiguity for an agent.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema has one optional profile_id with no description and 0% schema coverage. The description does not explain what profile_id means, how it affects the returned questions, or whether it should be provided. The name gives only a minimal clue.

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 conveys that the tool provides consent-first questions related to saving event preferences, which distinguishes it from save_event_preferences and get_event_preferences. However, it phrases this as a usage instruction rather than directly stating the tool's function.

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?

The description gives a clear when-to-use trigger: when a user wants consent-first questions before saving event preferences. It does not mention alternatives or exclusion cases, so it falls short of a 5.

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

All events toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

B3.2/5.0
Disambiguation4/5

Most tools map to distinct actions across search, recommendations, preferences, tickets, and feedback, with clear descriptions. The only real ambiguity is between recommend_events and recommend_events_for_user, plus some follow-up overlap, but boundaries are mostly clear.

Naming Consistency4/5

Tool names follow a consistent imperative verb_noun pattern and use snake_case throughout. Minor inconsistency exists in event vs events pluralization and interchangeable create/save verbs, but the overall pattern is predictable.

Tool Count3/5

23 tools is a large surface for an events assistant, landing in the 16-25 range that feels heavy. The count is defensible given the breadth of features, but it is borderline and somewhat difficult to navigate.

Completeness4/5

The set covers the core consumer journey well: search, recommendations, preference onboarding and CRUD, ticket quoting and purchase, and post-event feedback. Missing order-status or refund/cancellation endpoints are minor gaps, but primary workflows do not hit dead ends.

Resources