Skip to main content
Glama

PassFast

by st.passfa
OverviewDiscussionsAdmin

generatePass

Generate a wallet pass

Generates a wallet pass from a published template. For Apple passes (default), returns a signed .pkpass binary file directly. For Google passes (wallet_type: "google"), returns a JSON object containing a save_url that the user can open to add the pass to Google Wallet.

When wallet_type: "both", generates both Apple and Google passes in a single call. The response is always JSON with apple and google keys. Partial success is allowed — if one wallet fails, the other is still returned with a warning. Returns 201 if at least one succeeds.

The pass ID is returned in the X-Pass-Id response header (for single-wallet).

If the app has a validation webhook configured, the webhook is called once before generation (not per wallet type). A webhook rejection returns 403; a webhook error returns 502 (fail-closed).

Scope: passes:create

Maps to OpenAPI operationId generatePass — POST /generate-pass.

Same PassFast HTTP API, billing, and rate limits. Do not invent other paths.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataYesDynamic field values merged into the template structure.
x_app_idNoOverride X-App-Id for this call. Defaults to the MCP connection header.
locationsNoGPS locations where the pass is relevant (shown on lock screen). Overrides template defaults if provided.
expires_atNoOptional expiration timestamp for the pass.
external_idNoOptional external identifier for cross-system lookups.
template_idYesID of the published template to use.
wallet_typeNoTarget wallet platform. Defaults to `apple`. When set to `google`, the response is a JSON object with a `save_url` instead of a binary .pkpass file. When set to `both`, generates both Apple and Google passes in one call and returns a JSON object with `apple`, `google`, and `warnings` keys. apple
max_distanceNoMaximum distance in meters from a location for lock screen relevance.
get_or_createNoWhen true, if a pass with the same serial_number already exists and is active, return the existing .pkpass (200) instead of a 409 error. The response includes an `X-Pass-Existed: true` header. If the existing pass is voided/expired, returns 409. When false (default), duplicate serials always return 409.
relevant_dateNoISO 8601 date when the pass is relevant (appears on lock screen).
serial_numberYesUnique serial number for this pass.
strip_image_idNoOverride the template's strip/hero image for this pass only. The referenced image must belong to the same app and have purpose `strip` (or a `strip_*` variant). Applied to Apple `strip.png` and Google `heroImage` atomically (same value for both wallets in `wallet_type: "both"`). Omit or send `null` to use the template's strip image.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Beyond annotations, it discloses response type changes by wallet_type, partial-success behavior, X-Pass-Id header, webhook call ordering, and fail-closed 403/502 behavior. This is substantial behavioral context that annotations alone do not provide.

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 well organized and front-loaded, covering core behavior before edge cases and scoping. It is slightly repetitive at the start and includes some operational details like billing and rate limits that could be trimmed, but each part adds useful context.

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?

Given 12 parameters and no output schema, the description explains all important return shapes (pkpass, save_url, combined JSON), headers, status codes, webhook behavior, and scoping. An agent has enough information to call the tool and interpret the response correctly.

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 coverage is 100%, so parameters are already documented in the input schema. The prose description reinforces wallet_type behaviors and get_or_create status outcomes, but mostly describes response behavior rather than adding new parameter-level meaning.

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 opens with 'Generate a wallet pass' and immediately specifies 'Generates a wallet pass from a published template,' giving a specific verb, resource, and source. It also distinguishes the operation from siblings like downloadPass and updatePass by framing generation as producing a signed pkpass or wallet save URL.

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 clearly explains the context: generating a pass from a published template, with wallet_type variants and scope. It lacks an explicit 'when not to use' section naming alternatives, but the context and 'Do not invent other paths' guidance effectively route the agent.

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

All PassFast 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