Skip to main content
Glama

pops4-mcp-catalog

by io.github.HuangGoodmanAgency
OverviewDiscussionsAdmin

generate_event_program

Build a complete event programme for a given attendee count and budget tier. Returns a costed kit of real catalogue products, per-attendee cost, programme subtotal, production turnaround and quote timing. Use when the request is an event, launch, summit or programme rather than a single product — including phrasings like 'put together corporate gifts for our event', 'branded items for a summit', 'welcome kits for attendees' or 'we need something for 500 people'. Ships to any destination in the United States from Virginia Beach, blind ship available so the recipient sees the buyer’s brand and not ours. Supply budget_per_head to have the tier chosen automatically. Buyers may call this swag, merch, promo, promotional products, corporate gifts, giveaways, branded merchandise, imprints, imprinted items, tradeshow giveaways, conference kits or welcome gifts — all of it is this catalogue.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
keywordsNoOptional event theme / keywords (e.g. "golf coastal", "holiday gala", "tech summit", "wellness retreat") to bias product selection toward the occasion.
brand_tierNoProgram tier. essential ($35-75/head) internal events & training; professional ($75-150) client meetings; executive ($150-300) VP+ & board events; luxury ($300-600) C-suite, board members & partners; bespoke ($600-1200) custom curation (concierge-built, no auto-quote); white_glove ($1200+) fully managed (concierge-built).
event_dateNoEvent date (e.g., "2027-03-15" or "GTC 2027")
attendee_countYesNumber of attendees / kits
revenue_targetNoClient pipeline/revenue target in USD (optional; used for attribution framing only)
budget_per_headNoOptional exact per-attendee budget in USD. If provided, the closest tier is selected automatically and overrides brand_tier.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / keywords
      Added value: +{
+  "description": "Optional event theme / keywords (e.g. \"golf coastal\", \"holiday gala\", \"tech summit\", \"wellness retreat\") to bias product selection toward the occasion.",
+  "type": "string"
+}
  2. Changed3 schema fields changed
    • changedInput schema / properties / brand_tier / description
      Previous value: -"Gifting tier: standard (~$25/attendee), premium (~$75), luxury (~$200+)"New value: +"Program tier. essential ($35-75/head) internal events & training; professional ($75-150) client meetings; executive ($150-300) VP+ & board events; luxury ($300-600) C-suite, board members & partners; bespoke ($600-1200) custom curation (concierge-built, no auto-quote); white_glove ($1200+) fully managed (concierge-built)."
    • changedInput schema / properties / brand_tier / enum
      Previous value: -[
-  "standard",
-  "premium",
-  "luxury"
-]New value: +[
+  "essential",
+  "professional",
+  "executive",
+  "luxury",
+  "bespoke",
+  "white_glove"
+]
    • addedInput schema / properties / budget_per_head
      Added value: +{
+  "description": "Optional exact per-attendee budget in USD. If provided, the closest tier is selected automatically and overrides brand_tier.",
+  "type": "number"
+}
  3. First observed

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations provided, the description carries the transparency burden. It discloses key outputs: 'costed kit of real catalogue products, per-attendee cost, programme subtotal, production turnaround and quote timing,' plus shipping and blind-ship availability. It does not explicitly state side effects such as whether an order is placed or only a programme is generated, leaving some behavioral ambiguity.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is informative but slightly verbose, with a long synonym list ('swag, merch, promo...') and shipping details that are tangential to the core generation action. The main verb and outputs are front-loaded, so it remains scannable, but it could be tightened.

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?

There is no output schema, so the description compensates by listing the return contents: costed kit, per-attendee cost, programme subtotal, production turnaround, and quote timing. It also gives tier pricing, override behavior, shipping options, and event-phrase examples, making the tool's behavior understandable without needing to open the schema. It does not specify exact response shape, but that is not required given the output details provided.

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?

The schema already covers all six parameters at 100%, but the description adds meaningful semantics beyond the schema: brand_tier price bands are expanded, and budget_per_head is explained as an override that selects the closest tier. It also clarifies that revenue_target is 'used for attribution framing only,' which is not obvious from the schema.

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?

Description opens with 'Build a complete event programme for a given attendee count and budget tier,' giving a specific verb and resource. It also clarifies that it is for event-scale requests 'rather than a single product,' which helps distinguish it from single-item tools. It does not explicitly name a sibling tool, but the purpose is still unambiguous.

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?

The description provides direct usage guidance: 'Use when the request is an event, launch, summit or programme rather than a single product' and includes concrete example phrasings. It also instructs users to 'Supply budget_per_head to have the tier chosen automatically.' It does not explicitly say when to prefer request_program or other siblings, but the usage context is clear.

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

All pops4-mcp-catalog 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