Skip to main content
Glama

Preview loyalty card designs

preview_card_designs
Read-onlyIdempotent

Renders one to four loyalty card designs as Apple Wallet and Google Wallet passes so the person can compare them and pick one. Checks each design against Leal's rules and flags hard-to-read colour combinations. Returns a shareable preview link per design. Works without a Leal account; nothing is saved.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "designs": "<designs>"
    },
    "name": "preview_card_designs"
  }
}

Input Schema

NameRequiredDescriptionDefault
intentNoOptional. One short sentence on what the person asked you to do, e.g. "Set up a stamp card for Ground Up Café". Leal shows it in the person's activity log under Settings → AI agents, so they can see what was done for them. Leave out customer details.
designsYesThe designs to show side by side.
store_nameNoThe business name, shown where the pass shows the store.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • changedInput schema / properties / designs / items / properties / card_color / description
      Previous value: -"Pass background colour, hex (#RRGGBB)."New value: +"Pass background colour, hex (#RRGGBB). Fills the whole screen in Google Wallet, so avoid neon, fully saturated colours such as #00ff00."
    • addedInput schema / properties / designs / items / properties / google_hero_image_url
      Added value: +{
      +  "description": "Public https URL of a nearly square photo (1032×812, about 5:4) for Google Wallet's hero image, with no text in it. The stamps are drawn on top. Optional: without it the hero uses the strip background.",
      +  "type": "string"
      +}
    • addedInput schema / properties / designs / items / properties / google_logo_style
      Added value: +{
      +  "description": "How the logo sits on Google Wallet. round (default): square_logo_url in a circle with the store name. wide: logo_url in place of the circle and store name, best for wordmarks.",
      +  "enum": [
      +    "round",
      +    "wide"
      +  ],
      +  "type": "string"
      +}
    • changedInput schema / properties / designs / items / properties / strip_image_url / description
      Previous value: -"Public https URL of a wide photo for the strip (strip_type image), e.g. a hero image from the brand's website. Cropped to 375×144."New value: +"Public https URL of a wide photo for the strip (strip_type image), e.g. a hero image from the brand's website. Cropped to 375×144 on Apple Wallet; Google Wallet shows the middle of it in its nearly square hero unless google_hero_image_url is given."
    • changedInput schema / properties / designs / items / properties / text_color / description
      Previous value: -"Colour of all text on the pass, hex. Must read clearly on card_color (4.5:1 contrast or better)."New value: +"Colour of all text on the Apple pass, hex. Must read clearly on card_color (4.5:1 contrast or better). Google Wallet ignores it and picks black or white itself."
  2. Changed1 schema field changed
    • addedInput schema / properties / intent
      Added value: +{
      +  "description": "Optional. One short sentence on what the person asked you to do, e.g. \"Set up a stamp card for Ground Up Café\". Leal shows it in the person's activity log under Settings → AI agents, so they can see what was done for them. Leave out customer details.",
      +  "type": "string"
      +}
  3. Changed4 schema fields changed
    • addedInput schema / properties / designs / items / properties / qr_style
      Added value: +{
      +  "description": "What the pass QR holds. link (default for new cards): a phone camera opens the store's sign-up page with this customer as referrer, and the store scanner still reads it. code: the bare card code only. Passes showing the old QR keep scanning.",
      +  "enum": [
      +    "link",
      +    "code"
      +  ],
      +  "type": "string"
      +}
    • addedInput schema / properties / designs / items / properties / referee_stamps
      Added value: +{
      +  "description": "Stamps the invited friend gets on their first stamped visit. Less than stamps_required. Default 1.",
      +  "minimum": 0,
      +  "type": "integer"
      +}
    • addedInput schema / properties / designs / items / properties / referrals_enabled
      Added value: +{
      +  "description": "Let customers invite friends from the back of their pass. Both get stamps once the store first stamps the friend's card on a visit, never just for signing up. Default false.",
      +  "type": "boolean"
      +}
    • addedInput schema / properties / designs / items / properties / referrer_stamps
      Added value: +{
      +  "description": "Stamps the inviting customer gets when their friend's first visit is stamped. Less than stamps_required. Default 1.",
      +  "minimum": 0,
      +  "type": "integer"
      +}
  4. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Beyond the readOnly/idempotent/non-destructive annotations, the description discloses the validation pass ('Checks each design against Leal's rules and flags hard-to-read colour combinations'), the return value (a shareable preview link per design), and two operational facts: no Leal account needed and nothing is persisted. That is exactly the extra context annotations cannot convey.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Four short sentences, front-loaded with what it does before the side effects and return value. Every sentence carries distinct information - scope, validation, output, persistence - with no repetition of the title.

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

Completeness4/5

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

With no output schema, the description does cover the return shape at a high level (a preview link per design plus rule/contrast flags) and covers persistence and auth. The exact structure of the validation feedback is left unspecified, which is a minor gap for an agent that must report results back.

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%, so all three top-level parameters (designs, store_name, intent) are already documented in detail. The description adds only the 1-4 design cardinality, which merely echoes the schema's minItems/maxItems, and says nothing about how individual design fields are validated.

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?

States a specific verb and resource ('Renders ... loyalty card designs as Apple Wallet and Google Wallet passes') plus scope (one to four) and the user-facing goal of comparison. It does not name create_card or list_design_options, but 'nothing is saved' implicitly separates it from the creation siblings.

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?

'so the person can compare them and pick one' establishes the pre-creation, decision-support context, and 'Works without a Leal account' removes a prerequisite the agent might otherwise assume. There is no explicit when-not-to-use clause or named alternative for the actual creation step.

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