Skip to main content
Glama
Sign In

Generate Greetings

by com.generategreetings
OverviewDiscussionsAdmin

Write a greeting

generate_greeting

Generate a short, coherent, family-friendly greeting for an occasion. Returns complete phrases from curated language collections. Optional first name stays transient. Does not send or publish anything.

Input Schema

NameRequiredDescriptionDefault
nameNoOptional first name, up to 30 characters. Omit sensitive or identifying details. Never stored with a shared design.
styleNoWriting and visual style: sweet and tender, cheerful, simple and elegant, or motivational. The selected style changes the actual greeting wording.sweet
localeNoLanguage code; hi is Hindi. Use list_greeting_options for supported languages.en
occasionNomorning
previousCodesNoRecent phrase codes from this conversation to avoid repeats; do not send chat history.

Output Schema

NameRequiredDescriptionDefault
codeYes
textYes
localeYes
occasionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / previousCodes / items / pattern
      Previous value: -"^[a-z]+:[a-z]+:\\d+:\\d+:\\d+$"New value: +"^[a-z]+:[a-z]+:\\d+:\\d+:\\d+(?::(?:sweet|cheerful|simple|motivational))?$"
    • addedInput schema / properties / style
      Added value: +{
+  "default": "sweet",
+  "description": "Writing and visual style: sweet and tender, cheerful, simple and elegant, or motivational. The selected style changes the actual greeting wording.",
+  "enum": [
+    "sweet",
+    "cheerful",
+    "simple",
+    "motivational"
+  ],
+  "type": "string"
+}
    • changedOutput schema / properties / code / pattern
      Previous value: -"^(?:it|en|fr|es|de|pt|ar|zh|ja|ko|th|ru|hi|el|he):(?:morning|afternoon|evening|night|birthday|congratulations|christmas|newyear|lunarnewyear|mothersday|fathersday|weddinganniversary|anniversary|ramadan|eid|thankyou|getwell|wedding|newbaby|graduation|baptism|firstcommunion|confirmation|barmitzvah|hanukkah|roshhashanah|pesach|eidaladha|diwali|vesak):\\d+:\\d+:\\d+$"New value: +"^(?:it|en|fr|es|de|pt|ar|zh|ja|ko|th|ru|hi|el|he):(?:morning|afternoon|evening|night|birthday|congratulations|christmas|newyear|lunarnewyear|mothersday|fathersday|weddinganniversary|anniversary|ramadan|eid|thankyou|getwell|wedding|newbaby|graduation|baptism|firstcommunion|confirmation|barmitzvah|hanukkah|roshhashanah|pesach|eidaladha|diwali|vesak):\\d+:\\d+:\\d+(?::(?:sweet|cheerful|simple|motivational))?$"
  2. Changed5 schema fields changed
    • changedInput schema / properties / locale / enum
      Previous value: -[
-  "it",
-  "en",
-  "fr",
-  "es",
-  "de",
-  "pt",
-  "ar",
-  "zh",
-  "ja",
-  "ko",
-  "th",
-  "ru",
-  "hi",
-  "el"
-]New value: +[
+  "it",
+  "en",
+  "fr",
+  "es",
+  "de",
+  "pt",
+  "ar",
+  "zh",
+  "ja",
+  "ko",
+  "th",
+  "ru",
+  "hi",
+  "el",
+  "he"
+]
    • changedInput schema / properties / occasion / enum
      Previous value: -[
-  "morning",
-  "afternoon",
-  "evening",
-  "night",
-  "birthday",
-  "congratulations",
-  "christmas",
-  "newyear",
-  "lunarnewyear",
-  "mothersday",
-  "fathersday",
-  "weddinganniversary",
-  "anniversary",
-  "ramadan",
-  "eid",
-  "thankyou",
-  "getwell",
-  "wedding",
-  "newbaby",
-  "graduation"
-]New value: +[
+  "morning",
+  "afternoon",
+  "evening",
+  "night",
+  "birthday",
+  "congratulations",
+  "christmas",
+  "newyear",
+  "lunarnewyear",
+  "mothersday",
+  "fathersday",
+  "weddinganniversary",
+  "anniversary",
+  "ramadan",
+  "eid",
+  "thankyou",
+  "getwell",
+  "wedding",
+  "newbaby",
+  "graduation",
+  "baptism",
+  "firstcommunion",
+  "confirmation",
+  "barmitzvah",
+  "hanukkah",
+  "roshhashanah",
+  "pesach",
+  "eidaladha",
+  "diwali",
+  "vesak"
+]
    • changedOutput schema / properties / code / pattern
      Previous value: -"^(?:it|en|fr|es|de|pt|ar|zh|ja|ko|th|ru|hi|el):(?:morning|afternoon|evening|night|birthday|congratulations|christmas|newyear|lunarnewyear|mothersday|fathersday|weddinganniversary|anniversary|ramadan|eid|thankyou|getwell|wedding|newbaby|graduation):\\d+:\\d+:\\d+$"New value: +"^(?:it|en|fr|es|de|pt|ar|zh|ja|ko|th|ru|hi|el|he):(?:morning|afternoon|evening|night|birthday|congratulations|christmas|newyear|lunarnewyear|mothersday|fathersday|weddinganniversary|anniversary|ramadan|eid|thankyou|getwell|wedding|newbaby|graduation|baptism|firstcommunion|confirmation|barmitzvah|hanukkah|roshhashanah|pesach|eidaladha|diwali|vesak):\\d+:\\d+:\\d+$"
    • changedOutput schema / properties / locale / enum
      Previous value: -[
-  "it",
-  "en",
-  "fr",
-  "es",
-  "de",
-  "pt",
-  "ar",
-  "zh",
-  "ja",
-  "ko",
-  "th",
-  "ru",
-  "hi",
-  "el"
-]New value: +[
+  "it",
+  "en",
+  "fr",
+  "es",
+  "de",
+  "pt",
+  "ar",
+  "zh",
+  "ja",
+  "ko",
+  "th",
+  "ru",
+  "hi",
+  "el",
+  "he"
+]
    • changedOutput schema / properties / occasion / enum
      Previous value: -[
-  "morning",
-  "afternoon",
-  "evening",
-  "night",
-  "birthday",
-  "congratulations",
-  "christmas",
-  "newyear",
-  "lunarnewyear",
-  "mothersday",
-  "fathersday",
-  "weddinganniversary",
-  "anniversary",
-  "ramadan",
-  "eid",
-  "thankyou",
-  "getwell",
-  "wedding",
-  "newbaby",
-  "graduation"
-]New value: +[
+  "morning",
+  "afternoon",
+  "evening",
+  "night",
+  "birthday",
+  "congratulations",
+  "christmas",
+  "newyear",
+  "lunarnewyear",
+  "mothersday",
+  "fathersday",
+  "weddinganniversary",
+  "anniversary",
+  "ramadan",
+  "eid",
+  "thankyou",
+  "getwell",
+  "wedding",
+  "newbaby",
+  "graduation",
+  "baptism",
+  "firstcommunion",
+  "confirmation",
+  "barmitzvah",
+  "hanukkah",
+  "roshhashanah",
+  "pesach",
+  "eidaladha",
+  "diwali",
+  "vesak"
+]
  3. Changed3 schema fields changed
    • changedInput schema / properties / locale / enum
      Previous value: -[
-  "it",
-  "en",
-  "fr",
-  "es",
-  "de",
-  "pt",
-  "ar",
-  "zh",
-  "ja",
-  "ko",
-  "th",
-  "ru",
-  "hi"
-]New value: +[
+  "it",
+  "en",
+  "fr",
+  "es",
+  "de",
+  "pt",
+  "ar",
+  "zh",
+  "ja",
+  "ko",
+  "th",
+  "ru",
+  "hi",
+  "el"
+]
    • changedOutput schema / properties / code / pattern
      Previous value: -"^(?:it|en|fr|es|de|pt|ar|zh|ja|ko|th|ru|hi):(?:morning|afternoon|evening|night|birthday|congratulations|christmas|newyear|lunarnewyear|mothersday|fathersday|weddinganniversary|anniversary|ramadan|eid|thankyou|getwell|wedding|newbaby|graduation):\\d+:\\d+:\\d+$"New value: +"^(?:it|en|fr|es|de|pt|ar|zh|ja|ko|th|ru|hi|el):(?:morning|afternoon|evening|night|birthday|congratulations|christmas|newyear|lunarnewyear|mothersday|fathersday|weddinganniversary|anniversary|ramadan|eid|thankyou|getwell|wedding|newbaby|graduation):\\d+:\\d+:\\d+$"
    • changedOutput schema / properties / locale / enum
      Previous value: -[
-  "it",
-  "en",
-  "fr",
-  "es",
-  "de",
-  "pt",
-  "ar",
-  "zh",
-  "ja",
-  "ko",
-  "th",
-  "ru",
-  "hi"
-]New value: +[
+  "it",
+  "en",
+  "fr",
+  "es",
+  "de",
+  "pt",
+  "ar",
+  "zh",
+  "ja",
+  "ko",
+  "th",
+  "ru",
+  "hi",
+  "el"
+]
  4. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "code": {
+      "maxLength": 100,
+      "pattern": "^(?:it|en|fr|es|de|pt|ar|zh|ja|ko|th|ru|hi):(?:morning|afternoon|evening|night|birthday|congratulations|christmas|newyear|lunarnewyear|mothersday|fathersday|weddinganniversary|anniversary|ramadan|eid|thankyou|getwell|wedding|newbaby|graduation):\\d+:\\d+:\\d+$",
+      "type": "string"
+    },
+    "locale": {
+      "enum": [
+        "it",
+        "en",
+        "fr",
+        "es",
+        "de",
+        "pt",
+        "ar",
+        "zh",
+        "ja",
+        "ko",
+        "th",
+        "ru",
+        "hi"
+      ],
+      "type": "string"
+    },
+    "occasion": {
+      "enum": [
+        "morning",
+        "afternoon",
+        "evening",
+        "night",
+        "birthday",
+        "congratulations",
+        "christmas",
+        "newyear",
+        "lunarnewyear",
+        "mothersday",
+        "fathersday",
+        "weddinganniversary",
+        "anniversary",
+        "ramadan",
+        "eid",
+        "thankyou",
+        "getwell",
+        "wedding",
+        "newbaby",
+        "graduation"
+      ],
+      "type": "string"
+    },
+    "text": {
+      "maxLength": 6000,
+      "minLength": 1,
+      "type": "string"
+    }
+  },
+  "required": [
+    "text",
+    "code",
+    "locale",
+    "occasion"
+  ],
+  "type": "object"
+}
  5. First observed

TDQS

A4/5.0
Behavior4/5

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

Beyond the annotations it discloses that output is 'complete phrases from curated language collections,' that the name is transient/not stored, and that it does not send or publish. These add real behavioral context the annotations don't cover. It doesn't address rate limits or how previousCodes affects output beyond avoiding repeats.

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, each earning its place: purpose and output nature up front, privacy note, and the non-sending scope constraint. No filler.

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?

Output schema exists, so return values needn't be explained; the description covers purpose, output origin, privacy, and side-effect scope. Forced-enum params (locale, occasion) rely on schema descriptions, which handle that. Broadly complete for a 5-param generative 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 coverage is 80%, so the schema already documents most parameters including enums and the previousCodes pattern. The description adds that name is transient and not persisted, which reinforces the schema note, but contributes little new per-parameter semantics.

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?

States a specific verb and resource ('generate a short, coherent, family-friendly greeting for an occasion') and is clearly distinct from siblings create_greeting_card (which presumably publishes) and list_greeting_options (which enumerates support).

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 implies usage for occasions and clarifies scope ('does not send or publish anything'), steering away from card creation, but it never names siblings or states explicit when-to-use conditions. Usage context is implied rather than stated.

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

All Generate Greetings 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