Skip to main content
Glama

Make a personalised video wish

make_wish

Prepares a personalised video wish: Santa Claus, Mrs Claus, an elf, Saint Nicholas, the Three Kings, the Tooth Fairy, a birthday bear or another character says a first name and a short message, in the chosen language. Returns the link to its page on cirrela.com, already filled in: there the person watches the whole video with the Cirrela mark before deciding anything, and can keep it without the mark with one payment on that page. Nothing is rendered or paid in the chat, and no sign-in is needed. A first name and words only: no photo, no real person's face or voice; the words can't hold a link, an address or a phone number. Fits requests such as "personalised Santa video for my son Leo", "vidéo personnalisée du Père Noël pour Emma", "video personalizado de Papá Noel para Lucía", "vídeo personalizado do Papai Noel para o João". Give the person the link.

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": {
      "name": "<name>",
      "language": "<language>"
    },
    "name": "make_wish"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesThe first name the video says, as it should be written (a child's first name is fine; never a surname or an address).
messageNoOptional: the exact words, with the first name in them, at most about 12 seconds spoken. Left out, the page offers the occasion's own words.
languageYesThe language spoken: en, fr, es, pt (Brazil), pt-PT (Portugal), hi, ar or id. Usually the language the person writes in.
occasionNoDefault santa. The occasion: santa (Santa Claus speaks to a child), nice-list (Santa tells a child they are on the Nice List, always kind), elf-arrival (a Christmas elf tells a child he is back for December), santa-reminder (Santa kindly encourages a child: bedtime, sharing or listening; never a threat), elf-magic (the family’s Christmas elf was touched: Santa tells the child the magic is mended and nobody is in trouble), elf-asleep (the elf forgot to move overnight: Santa says he was simply too tired), santa-exists (a child doubts Santa is real: Santa answers with warmth), gift-late (the Christmas gift hasn't arrived: Santa says it's on its way, a little late but worth the wait), santa-departs (Christmas Eve: Santa announces he is taking off with everyone's gifts), first-christmas (Santa, Mrs Claus or the elf welcomes the family's new baby to their first Christmas, saying the baby's name), baby-news (Santa announces a baby on the way to the person named: a grandparent, a big sibling, an aunt), elf-goodbye (24 December: the family's Christmas elf says goodbye to the child and flies home with Santa), saint-nicolas (Saint Nicholas, the bishop of 6 December in Belgium, the Netherlands, Alsace and Germany, speaks to a child), christmas (a reindeer, a snowman or Mrs Claus, for anyone), birthday, engagement (congratulates a couple by their names), wedding (wedding wishes or a toast from a guest who can't attend, with the couple's names), anniversary (a wedding anniversary, the couple's names), retirement (a happy retirement and thank-you, by name), new-year, tooth-fairy, three-kings (5 January), valentine, easter, mothers-day, fathers-day, eid, diwali, hanukkah.
characterNoOptional: who speaks, if the person chose (santa-cabin or santa-workshop for Santa, mrs-claus, elf, saint-nicolas, king-melchior, tooth-fairy, birthday-bear…). It must belong to the occasion; left out, the occasion's usual character.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Annotations only say this is a non-read-only, non-destructive, non-idempotent, closed-world call; the description supplies everything the annotations cannot: the output is a pre-filled page link, the preview is watermarked, the unmarked copy requires one payment on that page, nothing renders or charges in chat, and no sign-in is required. It also declares hard content limits (no photo, no real face or voice, no links/addresses/phone numbers), which is exactly the kind of behavioral context an agent needs before calling.

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-loads the action, then the deliverable, then the constraints, and closes with the operative instruction 'Give the person the link.' The four-language example set is longer than strictly necessary and slightly crowds a dense paragraph, but every sentence is on-task with no filler or marketing language.

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 five-parameter creation tool with no output schema, it covers what gets produced, what is returned (a link, not a rendered file), the payment boundary, the anonymity/content constraints, and linguistic scope. An agent could call it and act on the result with no further information.

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% and the enum descriptions are already rich, so the baseline would be 3. The description still adds value by restating the name/message boundary as a rule ('A first name and words only') and by tying character choice to occasion validity ('It must belong to the occasion'), which reinforces the schema's constraints rather than merely repeating them.

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 ('Prepares a personalised video wish'), enumerates the characters that can speak, and makes the deliverable concrete ('Returns the link to its page on cirrela.com'). It implicitly separates itself from rendering siblings by saying 'Nothing is rendered or paid in the chat', but it never names create_video/create_film as the alternative, so differentiation is inferential rather than explicit.

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 contexts with four multilingual example requests ('personalised Santa video for my son Leo', 'vidéo personnalisée du Père Noël pour Emma'), plus the follow-through instruction 'Give the person the link.' It lacks any explicit when-not-to-use or named alternative among the create_* siblings, which keeps it short of a 5.

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