Skip to main content
Glama

pops4-mcp-catalog

by io.github.HuangGoodmanAgency

generate_event_program

AI-native corporate gifting tool that builds Live event dashboard programs for Fortune 500 and semiconductor companies. Generates a complete event program from the live 70,000+ catalog for a given event date, attendee count, and brand tier: curated per-attendee kit, wholesale subtotal, per-attendee cost, and logistics (kitting + blind multi-site shipping). One-hour quote enterprise events, Ships in days Fortune 500, with Revenue attribution event programs.

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. Dates show when Glama detected each change.

  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

C2.8/5.0
Behavior2/5

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

With no annotations provided, the description must disclose behavioral traits. It mentions output components and timing ('One-hour quote', 'Ships in days') but does not state side effects, required permissions, whether it writes data, or limitations. The promotional tone obscures operational behavior.

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

Conciseness2/5

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

The description is short but poorly structured, with unnecessary marketing language ('AI-native', 'Fortune 500 and semiconductor companies') and a confusing final fragment. Key information is present but not front-loaded or clearly organized.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity and lack of output schema/annotations, the description should explain return values and edge cases. It lists main outputs but omits details like bespoke/white_glove handling (though present in schema) and does not clarify the 'Revenue attribution' aspect. The description gives a good overview but leaves gaps.

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 descriptions cover 100% of parameters, so the baseline is 3. The description only references event_date, attendee_count, and brand_tier, not keywords, budget_per_head, or revenue_target. It does not add information beyond the schema's detailed parameter descriptions.

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?

The description clearly states that the tool generates a complete event program with specific outputs (curated kit, wholesale subtotal, per-attendee cost, logistics). It names a distinct resource ('Live event dashboard programs') and verb ('builds'), but does not explicitly differentiate from sibling tools such as get_live_quote.

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

Usage Guidelines2/5

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

No explicit when-to-use guidance or alternatives are mentioned. It implies use for enterprise gifting events but does not explain when to prefer this over get_quote or get_live_quote. The phrase 'One-hour quote enterprise events' hints at urgency but is ambiguous and not actionable.

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
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

B3.4/5.0
Disambiguation2/5

get_quote and get_live_quote both return wholesale quotes for product SKUs and quantities, differing only in context (enterprise events vs. general). get_product_catalog and search_products both search the catalog with filters, making the boundary between them unclear. These overlaps can lead to agent misselection.

Naming Consistency4/5

All tools use snake_case with a verb_noun pattern (get_, generate_, search_, track_). There are minor deviations where similar actions use different verbs (e.g., get_product_catalog vs. search_products, get_quote vs. get_live_quote), but the overall pattern is consistent and predictable.

Tool Count5/5

With 10 tools, the server is well-scoped for its purpose. Each tool covers a distinct aspect of the procurement and event management domain, and the count falls within the ideal 3-15 range, earning its place without feeling bloated.

Completeness3/5

The server covers product discovery, catalog browsing, quotes, event program generation, and shipment tracking. However, there is no tool for placing an order or managing event records, and the link between quotes and orders is unclear, leaving notable gaps in the end-to-end procurement workflow.

Resources