Skip to main content
Glama

events

by xyz.urbanplayground
OverviewDiscussionsAdmin

Get Preference Onboarding

get_preference_onboarding
Read-onlyIdempotent

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.

  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.1/5.0
Behavior3/5

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

Annotations already communicate that this is a safe, read-only, idempotent operation, so the description's burden is lower. It adds modest behavioral context by noting the consent-first nature and that it precedes saving, but it does not disclose what the response contains, whether it is a list of questions, or how a caller should consume the result.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single compact sentence with no wasted words. However, it is framed entirely as a usage directive and never actually says what the tool does or returns, which makes it underspecified rather than genuinely concise.

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

Completeness2/5

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

The tool is low-complexity (one unrequired param, no nested objects), but there is no output schema, so the description should explain what the call returns; it does not. The profile_id parameter is also left entirely unexplained, leaving an agent without enough information to invoke the tool correctly.

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

Parameters1/5

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

Schema description coverage is 0% and the lone parameter, profile_id, is completely undocumented in the description. With coverage that low, the description was required to compensate, but it says nothing about the parameter's meaning, format, or why it is needed for onboarding.

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 implies the tool surfaces consent-first onboarding questions that precede saving event preferences, which distinguishes it from siblings like get_event_preferences (retrieve saved preferences) and save_event_preferences (persist them). It lacks a direct verb+resource statement like 'retrieve onboarding questions', but the intended purpose is inferable and differentiates well from the event-preference family.

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 explicitly states when to use the tool: when a user wants consent-first questions before saving event preferences. It gives clear context but does not name alternatives or state when not to use it, missing the full when/when-not articulation that would earn 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
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