list_greeting_optionsList supported greeting languages, occasions, styles, image formats and background categories. No personal data required.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
| Name | Required | Description | Default |
|---|---|---|---|
| price | Yes | ||
| styles | Yes | ||
| formats | Yes | ||
| privacy | Yes | ||
| languages | Yes | ||
| occasions | Yes | ||
| backgrounds | Yes | ||
| decorations | Yes |
Changes observed during successful MCP inspections.
Output schema / properties / languages / items / properties / code / enumPrevious 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"
+]Output schema / properties / occasions / items / properties / code / enumPrevious 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"
+]Output schema / properties / languages / items / properties / code / enumPrevious 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"
+]Output schema / properties / styles / items / enumPrevious value: -[
- "sweet",
- "cheerful",
- "simple"
-]New value: +[
+ "sweet",
+ "cheerful",
+ "simple",
+ "motivational"
+]Output schema / (root)Previous value: -nullNew value: +{
+ "$schema": "http://json-schema.org/draft-07/schema#",
+ "additionalProperties": false,
+ "properties": {
+ "backgrounds": {
+ "items": {
+ "enum": [
+ "auto",
+ "all",
+ "nature",
+ "flowers",
+ "animals",
+ "coffee",
+ "celebration",
+ "Mare",
+ "Laghi",
+ "Fiumi",
+ "Cascate",
+ "Montagne",
+ "Boschi",
+ "Deserti",
+ "Neve",
+ "Cieli",
+ "Prati"
+ ],
+ "type": "string"
+ },
+ "type": "array"
+ },
+ "decorations": {
+ "items": {
+ "enum": [
+ "random",
+ "none"
+ ],
+ "type": "string"
+ },
+ "type": "array"
+ },
+ "formats": {
+ "items": {
+ "enum": [
+ "9:16",
+ "4:5",
+ "1:1",
+ "16:9"
+ ],
+ "type": "string"
+ },
+ "type": "array"
+ },
+ "languages": {
+ "items": {
+ "additionalProperties": false,
+ "properties": {
+ "code": {
+ "enum": [
+ "it",
+ "en",
+ "fr",
+ "es",
+ "de",
+ "pt",
+ "ar",
+ "zh",
+ "ja",
+ "ko",
+ "th",
+ "ru",
+ "hi"
+ ],
+ "type": "string"
+ },
+ "name": {
+ "minLength": 1,
+ "type": "string"
+ }
+ },
+ "required": [
+ "code",
+ "name"
+ ],
+ "type": "object"
+ },
+ "type": "array"
+ },
+ "occasions": {
+ "items": {
+ "additionalProperties": false,
+ "properties": {
+ "code": {
+ "enum": [
+ "morning",
+ "afternoon",
+ "evening",
+ "night",
+ "birthday",
+ "congratulations",
+ "christmas",
+ "newyear",
+ "lunarnewyear",
+ "mothersday",
+ "fathersday",
+ "weddinganniversary",
+ "anniversary",
+ "ramadan",
+ "eid",
+ "thankyou",
+ "getwell",
+ "wedding",
+ "newbaby",
+ "graduation"
+ ],
+ "type": "string"
+ },
+ "name": {
+ "minLength": 1,
+ "type": "string"
+ }
+ },
+ "required": [
+ "code",
+ "name"
+ ],
+ "type": "object"
+ },
+ "type": "array"
+ },
+ "price": {
+ "minLength": 1,
+ "type": "string"
+ },
+ "privacy": {
+ "minLength": 1,
+ "type": "string"
+ },
+ "styles": {
+ "items": {
+ "enum": [
+ "sweet",
+ "cheerful",
+ "simple"
+ ],
+ "type": "string"
+ },
+ "type": "array"
+ }
+ },
+ "required": [
+ "languages",
+ "occasions",
+ "styles",
+ "formats",
+ "backgrounds",
+ "decorations",
+ "privacy",
+ "price"
+ ],
+ "type": "object"
+}Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description frames this as a plain listing operation, but annotations declare readOnlyHint=false and idempotentHint=false, implying possible state mutation and non-repeatable results. Those flags directly contradict what a 'List supported ... options' tool does. The one genuinely additive line, 'No personal data required,' does not offset the inconsistency.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two short sentences with zero waste. The enumerated return facets come first and the scope guarantee follows, so the definition is front-loaded and easy to scan.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
An output schema exists, so return values need no explanation, and the description adequately covers what the listing contains. The only shortfall is that it never addresses the read-only/idempotency expectation that the annotations muddy.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The tool takes zero parameters, which is the baseline-4 case; there is no parameter semantics to communicate and the empty schema matches the description's no-input framing.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb ('List') with a well-scoped resource and enumerates the exact facets returned (languages, occasions, styles, image formats, background categories). This is clearly a read-only discovery tool, distinguishable from the sibling create_greeting_card and generate_greeting which produce artifacts.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No explicit when-to-use guidance and no alternatives named. The natural workflow (call this before generate_greeting to learn valid option values) is left entirely to inference, and 'No personal data required' hints at context but is not a usage rule.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.