events

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

Name	Required	Description	Default
`profile_id`	No	Stable user/profile id if already known.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 14, 2026
- addedInput schema / properties / profile_id / description
```
Added value: +"Stable user/profile id if already known."
```
- addedInput schema / properties / profile_id / maxLength
```
Added value: +200
```

Changed2 schema fields changedAug 30, 2026

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

Changed2 schema fields changedAug 24, 2026

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"
+}

Changed2 schema fields changedAug 24, 2026

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

First observedJul 30, 2026

TDQS

C2.9/5.0

Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered by structured data. The description adds no behavioral context beyond that — no indication of what is returned, whether it is a static questionnaire, or any auth/consent prerequisites, despite 'consent-first' being the tool's distinguishing trait.

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?

A single front-loaded sentence with no padding, and the usage trigger comes first. It is efficient, though the phrasing 'wants consent-first questions' is slightly awkward and could have spent the same words stating what the tool actually returns.

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?

With no output schema and a read-only, optional-parameter design, the description should at minimum say what comes back (the onboarding questions) and whether they depend on profile_id. It gestures at the scenario but leaves the return contract implicit, which is a meaningful gap for a 'get' tool.

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 profile_id is already documented as 'Stable user/profile id if already known', so the schema carries parameter meaning. The description adds nothing about how profile_id affects the onboarding output (e.g. personalized vs generic questions), so baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/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 tied to event preferences, but it never states plainly that it returns onboarding questions or what that payload is. The verb+resource from the name ('get preference onboarding') is never restated in operational terms, and sibling routing (e.g. vs get_event_preferences, save_event_preferences) is only hinted at via 'before saving event preferences'.

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?

'Use this when a user wants consent-first questions before saving event preferences' gives a trigger scenario, which is real usage guidance. However it names no alternative tool and gives no exclusion conditions, so an agent still has to guess how this differs from get_event_preferences or create_event_preference_profile.

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

All events 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?