Panda Greetings

Make a card design

make_card_design

Use this when the user asks Panda Greetings to draw a new card design or picture, for example a card with a particular scene, rather than ready-made designs. Panda Greetings draws it from their description of the picture, else from their message, and puts the message inside. Each ChatGPT user gets 2 drawn free a month; after that, and in assistants that don't identify the user, it shows ready-made designs with the message instead. When the picture is already in the chat (attached, or one you made), use make_card_from_image instead. Drawing takes about a minute. The link opens the card on pandagreetings.com as a printed card, or one their team signs, ready to order. Always include the card's link in your reply.

Input Schema

TableJSON Schema

Name	Required	Description
`message`	No	The message the user wrote or approved, as it goes inside the card: a greeting and a sign-off with the names if known, else [Recipient] and [Your Name], which are filled in when they order.
`picture`	No	A short description of the picture to draw, if the user said what they want.
`to_name`	No	Who the card is for, if known.
`occasion`	No	What the card is for, if known. Pick the closest match; for a holiday, its own name (christmas, hanukkah, valentines-day…).
`from_name`	No	Who it is from, if known.
`from_group`	No	True when several people will sign it, such as a team card.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`note`	No
`group`	Yes
`price`	Yes
`status`	No
`arrival`	No
`designs`	Yes
`product`	Yes
`occasion`	Yes
`messageIncluded`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 4, 2026

changedInput schema / properties / message / description

Previous value: -"The message the user wrote or approved, to put inside the card."New value: +"The message the user wrote or approved, as it goes inside the card: a greeting and a sign-off with the names if known, else [Recipient] and [Your Name], which are filled in when they order."

addedOutput schema / properties / arrival

Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "orderedToday": {
+      "type": "string"
+    },
+    "priority": {
+      "type": "string"
+    },
+    "standard": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "orderedToday",
+    "standard",
+    "priority"
+  ],
+  "type": "object"
+}

First observedOct 4, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations only cover the safety profile (readOnly=false, destructive=false, idempotent=false, openWorld=false); the description adds the quota rule (2 free drawings per user per month), the degraded fallback path, the ~1 minute latency, and the mandatory follow-up action of including the link in the reply. These are real behavioral traits an agent could not infer from the structured fields.

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-loaded with the trigger condition and the sibling routing, and every sentence carries information (quota, latency, output link). Some sentences are long and chain multiple clauses, but there is no filler.

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?

Given an output schema exists, the description needn't explain return values, yet it still tells the agent what the link is and that it must be included in the reply. Alternatives, fallback behavior, quota, and latency are all covered, leaving no material gap for a 6-param, zero-required tool.

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 description coverage is 100%, so the baseline is 3, but the description adds genuine semantics beyond the schema: the picture is drawn from the user's stated scene 'else from their message', and the message is placed inside the card. It stops short of explaining the from_group or occasion handling beyond what the schema already says.

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 ('draw a new card design or picture') and immediately contrasts it with ready-made designs and with the sibling make_card_from_image. An agent can distinguish it from both siblings without opening a schema.

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

Usage Guidelines5/5

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

Gives explicit when-to-use (user asks for a drawn design, e.g. a particular scene), explicit when-not (picture already in chat → use make_card_from_image), and even the fallback condition (quota exhausted or unidentified user → ready-made designs). Nothing is left to inference.

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

All Panda Greetings tools Inspect

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

Need Help?