Skip to main content
Glama

Create a signup poster

create_poster

Creates a printable poster with a QR code for a card. Customers scan it, fill in a short form on a public Leal signup page, and add the card to their wallet. Returns the signup link and a print link. Colours default to the card's.

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": {
      "card_id": "<card_id>"
    },
    "name": "create_poster"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleNoHeadline, e.g. "Join our coffee club". Defaults to the card name.
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.
card_idYesCard id from list_cards.
paper_sizeNoDefault a4.
text_colorNoPoster text colour, hex. Defaults to the card's text colour.
primary_colorNoPoster background colour, hex. Defaults to the card colour.
secondary_colorNoAccent panel colour, hex.
require_birthdayNoAsk for a birthday (for birthday rewards). Default false.
contact_collection_modeNoWhat the signup form asks for. Default email_and_phone.

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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"
      +}
  2. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare the safety profile (readOnlyHint=false, destructiveHint=false, openWorldHint=true, idempotentHint=false), and the description usefully adds side-effect detail: a public-facing signup page is created and the call returns a signup link plus a print link. It does not say what happens on repeated calls or whether posters accumulate, which is the main remaining behavioral gap.

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?

Three tight sentences, front-loaded with the core action, then the customer flow, then the return values. No redundant or filler wording.

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 nine parameters, no output schema, and a public-facing side effect, the description covers the essential return values (signup link, print link) and the external exposure, which is what an agent most needs. It stops short of clarifying whether repeated invocations create duplicate posters or how the poster is delivered/rendered, which leaves a small gap for a non-idempotent creation tool.

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 every parameter already has inline documentation; the description's only extra hint is "Colours default to the card's", which the schema states for primary_color anyway. Baseline 3 is appropriate since the schema carries the parameter burden.

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?

Specific verb plus resource ("Creates a printable poster with a QR code for a card") and it goes further to describe the end-to-end artifact: a public signup page, wallet add, and the two links returned. The resource is plainly distinct from the sibling create_card/create_reward/create_location tools, so an agent can route without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description conveys the scenario (a physical poster driving customer self-signup) which implies when this tool is appropriate, but it never states an explicit when-to-use rule, prerequisites (e.g. card must exist / be published), or what to use instead if the agent only needs a link. Usage is inferred rather than stated.

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