Skip to main content
Glama

What a Wallet pass can do

pass_catalog
Read-onlyIdempotent

Answers what an Apple or Google Wallet pass can do, from the Sonar Connections pass catalog: every option Apple and Google offer a pass issuer. Call it first for any ask about what the pass shows or changing it, such as "put a note on the pass", "remove the note", "take the home page link off" or "on the pass, ask phones to go silent", then make the change with the pass setting it names. Use it for questions like "what can my pass do", "what can go on the front of my pass", "can links sit on the front of the pass", "I want a loyalty program", "a coupon that expires", "tickets I can subtract at a food festival" or "can I put a sponsor on the pass". Pass the person's words as question; wallet, passType, area and status narrow the rows. The reply lists at most 8 rows, front first, then says how many more match and which filter narrows them. Each row says what it is, what the holder sees, which wallets and pass types carry it, where it sits, and one status sentence for Sonar Connections today; read that sentence as given, including "not yet". With eventIdOrName, a person who may change that event's details hears which rows their event's pass carries; anyone else hears a general answer. It reads only: it changes no pass, draws no preview and promises no date.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "pass_catalog"
  }
}

Input Schema

NameRequiredDescriptionDefault
areaNoOptional: where it sits: front, back, details, list, lock screen or notification.
statusNoOptional: settable, built, not built, needs approval or cannot.
walletNoOptional: apple, google or both.
passTypeNoOptional: a pass type, for example eventTicket, generic, storeCard, coupon, loyalty, offer or giftCard.
questionNoThe person's question, in their words.
eventIdOrNameNoOptional: the event id or name, to hear which rows its pass carries.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior5/5

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

The description adds substantial behavior beyond the annotations: output is capped at 8 rows, ordered front first, includes a count of additional matches and the filter that narrows them, and each row reports categories plus a status sentence to be read literally. It also explains the event-scoped permission nuance and explicitly states that it reads only, draws no preview and promises no date.

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 front-loaded with purpose and usage, then moves through parameters, output shape and permission behavior. It is somewhat long and example-heavy, but the examples support retrieval and most sentences add operational detail.

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?

There is no output schema, so the description has to explain the reply shape, and it does: row limit, ordering, extra-match count, per-row contents and status semantics are all covered. It also covers read-only behavior, preview limitations, and event-scoped permission differences, making it complete for this tool.

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 schema already documents the parameters. The description still adds useful meaning: `question` should be the person’s words, the other fields narrow the returned rows, and `eventIdOrName` produces event-specific results only for people permitted to change that event.

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?

The description states a specific verb and resource: it answers what an Apple or Google Wallet pass can do from the Sonar Connections pass catalog. It also distinguishes the tool’s role by saying to call it first for questions about what the pass shows or changing it, then make changes with the named pass setting.

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?

It gives clear when-to-use guidance with multiple example questions and says to call it first before making a change. However, it does not name a specific sibling tool for the follow-up change, so the alternative is implied rather than explicit.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources