Sonar Connections

Add the event pass to Apple Wallet or Google Wallet

event_wallet_pass

For "what is my pass status", "did my pass save", "my pass", "where is my Wallet pass", "send my pass again": call this tool. Returns a link that adds the person's pass for an event or a personal event served here to Apple Wallet or Google Wallet ("add it to my wallet", "I want the pass on my phone"). Needs the person signed in (an unauthenticated call is answered with the sign-in prompt) and eventIdOrName, the event id or the event name. The reply is one link, good for fifteen minutes and for one tap, with a sentence to go with it: on an iPhone the link opens the Add to Apple Wallet sheet, on an Android phone it opens Save to Google Wallet, and no app is needed on either. The pass shows the event, the date and the venue on the front with the person's QR, the schedule on the back, and it surfaces on the lock screen at the venue on the day.

Input Schema

Name	Required	Description	Default
`eventIdOrName`	Yes	REQUIRED. The event id (lbtw_2026, test_wedding_a_garden) or the event NAME as the organizer or the hosts spell it.

Output Schema

Name	Required	Description	Default
`ok`	No
`link`	No
`error`	No
`state`	No
`message`	No
`servedBy`	No
`walletLink`	No
`suggestions`	No
`expiresInMinutes`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 11, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "anyOf": [
+    {
+      "required": [
+        "ok",
+        "link"
+      ]
+    },
+    {
+      "properties": {
+        "ok": {
+          "const": false
+        }
+      },
+      "required": [
+        "ok"
+      ]
+    },
+    {
+      "properties": {
+        "found": {
+          "const": false
+        }
+      },
+      "required": [
+        "found"
+      ]
+    },
+    {
+      "required": [
+        "error"
+      ]
+    }
+  ],
+  "properties": {
+    "error": {
+      "type": "string"
+    },
+    "expiresInMinutes": {
+      "type": "number"
+    },
+    "link": {
+      "type": "string"
+    },
+    "message": {
+      "type": "string"
+    },
+    "ok": {
+      "type": "boolean"
+    },
+    "servedBy": {
+      "type": "string"
+    },
+    "state": {
+      "type": "string"
+    },
+    "suggestions": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "walletLink": {
+      "type": [
+        "object",
+        "null"
+      ]
+    }
+  },
+  "type": "object"
+}

AddedOct 8, 2026

TDQS

A4.1/5.0

Behavior5/5

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

Goes well beyond the annotations: the auth requirement and the unauthenticated sign-in-prompt behavior, single-use single-tap link with a fifteen-minute lifetime, platform-specific behavior (Add to Apple Wallet sheet vs Save to Google Wallet, no app required), and what the pass actually contains. This is consistent with the declared idempotent=false/destructive=false hints and explains why the link cannot be reused.

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?

Front-loaded with the routing phrases, then behavior, then output shape, which is the right order for an agent. It is a single dense paragraph, and the closing sentence about QR position, back-of-pass schedule and lock-screen surfacing is pleasant context but not needed to invoke the tool correctly.

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

Completeness5/5

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

For a one-parameter tool with an output schema, everything an agent needs is present: auth state handling, the one-link return with expiry, and platform differences. Nothing about calling it correctly is left to inference.

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 already documents both accepted forms (event id or event name as the organizer spells it). The description only restates that `eventIdOrName` is required, adding no resolution rules for ambiguous names, so the baseline 3 applies.

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 states a concrete verb+resource: it returns a link that adds a person's event pass to Apple Wallet or Google Wallet, with the effect spelled out. It is easy to tell apart from the surrounding site/biz tools, but it never distinguishes itself from the close siblings event_pass_reissue and event_pass_revoke, and even claims the phrase "send my pass again", which plausibly overlaps with reissue.

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?

Usage is anchored in explicit user phrasings ("what is my pass status", "where is my Wallet pass", "add it to my wallet") plus the precondition that the person must be signed in. There is no when-not or named-alternative routing, so an agent cannot resolve the reissue/revoke overlap from the description alone.

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?