Skip to main content
Glama
Sign In

Panda Greetings

by com.pandagreetings
OverviewDiscussionsAdmin

Server Details

Printed greeting cards: find designs with your message inside, then order on our site.

If you are the author of this connector, you can claim ownership by verifying the domain or GitHub account it belongs to. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
Status
Healthy
Uptime
100.0% over 28 days
Last Tested
Transport
Streamable HTTP · MCP 2025-11-25
URL

TDQS

A4.5/5.0

Scored across 1 tool

Disambiguation5/5

With only one tool in the set, there is no possibility of selecting the wrong tool or confusing overlapping purposes; the tool's scope (finding printed card designs for an occasion) is clearly stated and explicitly bounded by what it does not cover.

Naming Consistency4/5

The single tool name find_card_designs follows a clean, predictable verb_noun snake_case convention. Consistency across a set of one cannot really be demonstrated, but nothing deviates from the pattern.

Tool Count3/5

A one-tool surface is thin even for a narrow service; there is no separate operation for browsing occasions, retrieving a specific design, or checking shipping options independently. The narrow domain keeps it from being a severe mismatch, but it is borderline rather than well-scoped.

Completeness3/5

The tool covers the core find-designs workflow and pushes ordering/editing to external links, which limits dead ends for that single path. However, there are noticeable gaps such as looking up a specific design, browsing by category or price, or any order-related follow-up, leaving the surface minimal for the stated card domain.

Available Tools

1 tool
find_card_designsFind card designsA
Read-onlyIdempotent
Inspect

Finds ready-made Panda Greetings printed card designs for an occasion, for when the user wants a greeting card or card designs from Panda Greetings, such as a farewell card a team signs or a birthday card for their mom. Takes the occasion, whether several people will sign it, and the card message if there is one, which is placed inside each design. Returns up to four designs, each with a link that opens it on pandagreetings.com with the message inside, ready to edit and order as a printed card, or as a printed card a whole team signs from one link; Panda Greetings prints it and mails it in the US. Also returns the day a card ordered today would arrive with free Standard and with Priority shipping. It doesn't cover e-cards, gift cards, flowers or other gifts, or a text or chat message that isn't a card.

NameRequiredDescriptionDefault
messageNoThe card 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. Leave it out if there isn't one yet.
occasionYesWhat the card is for. Pick the closest match; for a holiday, its own name (christmas, hanukkah, valentines-day…), and holiday only when no other fits.
from_groupNoTrue when several people will sign it, such as a team card for a coworker or a class card for a teacher.

Output Schema

NameRequiredDescription
noteNo
groupYes
priceYes
statusNo
arrivalNo
designsYes
productYes
occasionYes
rememberNo
messageIncludedYes

TDQS

A4.8/5.0
Behavior5/5

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

Annotations only declare the safe-read profile (readOnly, idempotent, closed-world); the description goes well beyond that by disclosing the result cap (up to four designs), the per-design link behavior, the one-link team-signing mode, the fact that Panda Greetings prints and mails in the US only, and that shipping-arrival dates for free Standard and Priority are returned. These are operational constraints an agent could not derive from the annotations or schema.

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?

The core purpose and target user are front-loaded in the first clause, and every subsequent sentence adds scope, exclusions or delivery behavior. It is dense and runs long in a single paragraph, with mild repetition of 'Panda Greetings', but no sentence is 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?

For a three-parameter lookup with an output schema already covering return shape, the description supplies the remaining context an agent needs: the occasion/message/group semantics, the four-design cap, the ordering and mailing model, the US-only constraint, and the exclusions. Nothing material is missing.

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 meaning: it clarifies that the message is placed inside each design and that the boolean flag means several people will sign it. It maps all three parameters to user-facing intent rather than merely restating field names.

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 (Finds) and resource (ready-made Panda Greetings printed card designs) scoped to an occasion, and immediately bounds the domain by excluding e-cards, gift cards, flowers and non-card messages. An agent can tell exactly what this tool returns 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 Guidelines5/5

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

Gives an explicit use condition (when the user wants a greeting card or card designs from Panda Greetings) with concrete examples (farewell card a team signs, birthday card for mom), and an explicit when-not list (e-cards, gift cards, flowers, other gifts, plain text/chat messages). Nothing is left to inference even though there are no sibling tools to route to.

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

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 1 tool update
    • Changedfind_card_designs1 field changed
      • addedOutput schema / properties / remember
        Added value: +{
+  "type": "string"
+}
  2. 2 tool updates
    • Removedmake_card_design
    • Removedmake_card_from_image
  3. 3 tool updates
    • Changedfind_card_designs2 fields changed
      • changedInput schema / properties / message / description
        Previous value: -"The card message the user wrote or approved, to put inside the card. Leave it out if there isn't one yet."New value: +"The card 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. Leave it out if there isn't one yet."
      • addedOutput schema / properties / arrival
        Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "orderedToday": {
+      "type": "string"
+    },
+    "priority": {
+      "type": "string"
+    },
+    "standard": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "orderedToday",
+    "standard",
+    "priority"
+  ],
+  "type": "object"
+}
    • Changedmake_card_design2 fields changed
      • 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"
+}
    • Changedmake_card_from_image2 fields changed
      • 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"
+}
  4. 3 tool updates
    • First observedfind_card_designs
    • First observedmake_card_design
    • First observedmake_card_from_image

Related MCP Connectors

Related MCP Servers

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