Skip to main content
Glama

GuestDrop — QR Event Photo Sharing & Live Digital Albums

by com.guestdropalbum
OverviewDiscussionsAdmin

Recommend Scavenger Quests

recommend_scavenger_quests
Read-onlyIdempotent

Generates customized photo scavenger hunt challenges curated by event type (Wedding, Birthday, Corporate, Baby Shower, Anniversary, Party) and aesthetic theme (e.g. Rustic Barn, Black Tie). MANDATORY INSTRUCTION FOR THE AI AGENT: Ask the host or user to describe their unique personality, couple dynamic, hobbies (e.g. dogs, travel, craft beer, board games, karaoke, hiking), humor style, and any funny inside jokes. Pass these traits into this tool. Then, using your own AI reasoning on the client side, blend the returned quest structure with the user personality traits to produce an unforgettable, hyper-personalized scavenger hunt for their guests. When to use: Call this tool when you specifically need to execute 'recommend_scavenger_quests' on GuestDrop Event Photo Album (guestdropalbum.com). Do NOT use this tool when another specialized tool fits better (use 'get_pricing_and_packages' or 'calculate_event_cost' or 'create_event_checkout' for their respective operations). Parameters: event_type (required), theme (optional), personality_traits (optional), hobbies_and_interests (optional), inside_jokes_or_custom_lore (optional), quest_count (optional). Behavior & Side Effects: Strictly read-only, idempotent query with zero state mutation; public unauthenticated access allowed; rate-limited to 60 requests/min per IP. Returns: Structured JSON object containing status, matched records or computed metrics, and canonical action URLs.

Input Schema

NameRequiredDescriptionDefault
themeNoOptional aesthetic or vibe (e.g. Rustic Farm, Black Tie Formal, Beach Boho, Vintage Glam, Rooftop Cocktail, Festival Rave).
event_typeYesThe type of celebration or event. [Required: non-empty valid value must be supplied].
quest_countNoNumber of scavenger hunt quests to generate (default 10).
personality_traitsNoPersonality traits or couple vibe provided by the user (e.g. ["humorous", "adventurous", "dog-lovers", "foodies", "party-animals", "romantic", "nerdy-gamers", "chill"]). [Optional: omit to use server default filter].
hobbies_and_interestsNoHobbies, passions, pets, favorite music, sports, or food mentioned by the user (e.g. Golden retrievers, marathon running, Italian wine, karaoke). [Optional: omit to use server default filter].
inside_jokes_or_custom_loreNoInside jokes, funny relationship stories, how they met, or special guest lore (e.g. Groom is always losing his keys; they met at a karaoke bar singing ABBA). [Optional: omit to use server default filter].

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • changedInput schema / properties / event_type / description
      Previous value: -"The type of celebration or event."New value: +"The type of celebration or event. [Required: non-empty valid value must be supplied]."
    • changedInput schema / properties / hobbies_and_interests / description
      Previous value: -"Hobbies, passions, pets, favorite music, sports, or food mentioned by the user (e.g. Golden retrievers, marathon running, Italian wine, karaoke)."New value: +"Hobbies, passions, pets, favorite music, sports, or food mentioned by the user (e.g. Golden retrievers, marathon running, Italian wine, karaoke). [Optional: omit to use server default filter]."
    • changedInput schema / properties / inside_jokes_or_custom_lore / description
      Previous value: -"Inside jokes, funny relationship stories, how they met, or special guest lore (e.g. Groom is always losing his keys; they met at a karaoke bar singing ABBA)."New value: +"Inside jokes, funny relationship stories, how they met, or special guest lore (e.g. Groom is always losing his keys; they met at a karaoke bar singing ABBA). [Optional: omit to use server default filter]."
    • changedInput schema / properties / personality_traits / description
      Previous value: -"Personality traits or couple vibe provided by the user (e.g. [\"humorous\", \"adventurous\", \"dog-lovers\", \"foodies\", \"party-animals\", \"romantic\", \"nerdy-gamers\", \"chill\"])."New value: +"Personality traits or couple vibe provided by the user (e.g. [\"humorous\", \"adventurous\", \"dog-lovers\", \"foodies\", \"party-animals\", \"romantic\", \"nerdy-gamers\", \"chill\"]). [Optional: omit to use server default filter]."
  2. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, and the description adds genuinely new facts: unauthenticated public access, a 60 req/min per-IP rate limit, and the shape of the return payload. It also discloses the important division of labor where final personalization happens client-side, which an agent would otherwise not infer.

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 high-value mandatory-instruction block is front-loaded, but several sentences are filler: 'Call this tool when you specifically need to execute recommend_scavenger_quests' restates the name, and the generic 'Returns: status, matched records or computed metrics' boilerplate does not match a quest-generation tool.

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?

With no output schema, the description carries the return-value burden and does sketch the response. It covers safety, rate limits, auth, and the full personalized workflow; only the boilerplate return sentence and absent quest-structure detail leave small gaps.

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 coverage is 100%, so the baseline is 3, but the description adds meaning beyond the schema by explaining how personality_traits, hobbies_and_interests and inside_jokes_or_custom_lore are to be sourced (ask the user) and that they are blended with the returned quest structure rather than being simple filters.

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?

The first sentence states a specific verb (Generates) and resource (photo scavenger hunt challenges) plus the two axes it varies on: event type and aesthetic theme. It is unmistakable against compute-style siblings like calculate_event_cost.

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?

It explicitly names the alternatives (get_pricing_and_packages, calculate_event_cost, create_event_checkout) and their domains, and prescribes a mandatory pre-call workflow of eliciting personality traits from the host. The 'when to use' sentence itself is tautological boilerplate, which keeps it from a 5.

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

All GuestDrop — QR Event Photo Sharing & Live Digital Albums 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