Sonar Connections

Refresh a Wallet pass with a new code

event_pass_reissue

Destructive

Gives a Wallet pass a new QR code: a pass that was photographed or shared, or a guest's pass that a host of a personal event or the organizer of an event wants refreshed. It also brings back a revoked pass. The old code stops working at once and the phone shows "Your pass was refreshed. The old code no longer works." Nothing is re-added: the same pass updates in place on an iPhone and on Android. Needs eventIdOrName (the event id or the event name). Without serialNumber it acts on the caller's own pass at that event; with one it acts on that pass, for a caller who is a host or the organizer. Returns the outcome in one sentence.

Input Schema

Name	Required	Description	Default
`serialNumber`	No	OPTIONAL. The pass serial (on the pass, ps_ and 24 characters). Omit for the caller's own pass.
`eventIdOrName`	Yes	REQUIRED. The event id or the event NAME as the organizer or the hosts spell it.

Output Schema

Name	Required	Description	Default
`ok`	No
`error`	No
`action`	No
`message`	No
`reached`	No
`revoked`	No
`servedBy`	No
`idempotent`	No
`tokenVersion`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 12, 2026

removedInput schema / properties / action

Removed value: -{
-  "description": "REQUIRED. reissue (a new code, and a revoked pass comes back) or revoke (the pass is voided).",
-  "enum": [
-    "reissue",
-    "revoke"
-  ],
-  "type": "string"
-}

changedInput schema / required

Previous value: -[
-  "eventIdOrName",
-  "action"
-]New value: +[
+  "eventIdOrName"
+]

Changed1 schema field changedOct 11, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "anyOf": [
+    {
+      "required": [
+        "ok",
+        "action",
+        "idempotent",
+        "tokenVersion",
+        "revoked",
+        "reached"
+      ]
+    },
+    {
+      "properties": {
+        "ok": {
+          "const": false
+        }
+      },
+      "required": [
+        "ok"
+      ]
+    },
+    {
+      "properties": {
+        "found": {
+          "const": false
+        }
+      },
+      "required": [
+        "found"
+      ]
+    },
+    {
+      "required": [
+        "error"
+      ]
+    }
+  ],
+  "properties": {
+    "action": {
+      "type": "string"
+    },
+    "error": {
+      "type": "string"
+    },
+    "idempotent": {
+      "type": "boolean"
+    },
+    "message": {
+      "type": "string"
+    },
+    "ok": {
+      "type": "boolean"
+    },
+    "reached": {
+      "type": "object"
+    },
+    "revoked": {
+      "type": "boolean"
+    },
+    "servedBy": {
+      "type": "string"
+    },
+    "tokenVersion": {
+      "type": "integer"
+    }
+  },
+  "type": "object"
+}

AddedOct 8, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Goes well beyond the annotations: the old code stops working immediately, the exact on-device message shown, and that the pass updates in place rather than being re-added. It also discloses the authorization model (self, or host/organizer when serialNumber is supplied), which the annotations do not carry.

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 action and the reason for it, and most sentences carry distinct information: scope, side effect, in-place behavior, permissions. The closing note that it returns the outcome in one sentence is largely redundant given the tool has an output schema.

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 destructive, non-idempotent mutation with an output schema, the description covers everything an agent needs: what changes, what stops working, that the pass is not re-added, who may act on whose pass, and which parameter selects the scope. Return values are handled by the output schema.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, and the description adds real value beyond it: serialNumber's presence changes both the target and the required caller role, and eventIdOrName accepts an id or the name as organizers/hosts spell it. The serial format detail (ps_ + 24 chars) is left to the schema.

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?

States a specific verb and resource: gives a Wallet pass a new QR code, and additionally un-revokes a revoked pass. This clearly separates it from siblings like event_pass_revoke and event_wallet_pass without requiring the reader to open either 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?

Gives concrete triggering situations (pass was photographed or shared, a guest's pass a host wants refreshed) and states the role conditions for acting on someone else's pass. It does not explicitly name alternatives such as event_pass_revoke for revoking or event_wallet_pass for obtaining a pass, so routing is implied rather than spelled out.

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?