Skip to main content
Glama
Sign In

Dream On Concierge

by com.dreamonsail
OverviewDiscussionsAdmin

Ask the owner

ask_owner

Pass a question or request to the owner when the fact sheet doesn't cover it (holiday pricing, discounts, contract/payment/cancellation terms, longer or shorter stays, special services, anything else). The guest's email is on file and used automatically.

Input Schema

NameRequiredDescriptionDefault
kindNocrew_question when the guest wants to ask Captain Rob or Chef Julia something (menus, diets, diving, itinerary ideas) — the owner forwards it to the crew; referral_lead for groups over 8 or 5-cabin/10-passenger requests
nameNoGuest's name
emailNoGuest's email for the owner's reply (defaults to the email the guest gave at the start)
contextNoDates, party size and anything else relevant from the conversation
questionYesThe guest's question or request, in full
requesterNoOptional: who this request is for, so the owner can follow up personally.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / kind / description
      Previous value: -"crew_question when the guest wants to ask Captain Rob or Chef Julia something (menus, diets, diving, itinerary ideas) — the owner forwards it and the crew may reply directly; referral_lead for groups over 8 or 5-cabin/10-passenger requests"New value: +"crew_question when the guest wants to ask Captain Rob or Chef Julia something (menus, diets, diving, itinerary ideas) — the owner forwards it to the crew; referral_lead for groups over 8 or 5-cabin/10-passenger requests"
  2. Changed2 schema fields changed
    • changedInput schema / properties / kind / description
      Previous value: -"referral_lead for groups over 8 or 5-cabin/10-passenger requests that the owner can refer to another yacht"New value: +"crew_question when the guest wants to ask Captain Rob or Chef Julia something (menus, diets, diving, itinerary ideas) — the owner forwards it and the crew may reply directly; referral_lead for groups over 8 or 5-cabin/10-passenger requests"
    • changedInput schema / properties / kind / enum
      Previous value: -[
-  "question",
-  "referral_lead"
-]New value: +[
+  "question",
+  "referral_lead",
+  "crew_question"
+]
  3. First observed

TDQS

A4.2/5.0
Behavior3/5

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

Annotations already declare non-read-only, non-destructive, non-idempotent, so the safety profile is covered. The description adds that the guest email is on file and applied automatically, which is useful, but it says nothing about what happens after the handoff (owner reply channel, latency, whether the agent sees a confirmation) or that repeated calls create separate messages.

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

Conciseness5/5

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

Two tight sentences, front-loaded with the when-to-use condition before the parenthetical examples. No filler and nothing that restates the tool name.

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?

Covers the escalation intent and the auto-filled email for a 6-parameter tool with a nested requester object. Since there is no output schema, it could say more about the expected response or turnaround, but for a fire-and-forget handoff tool it is largely sufficient.

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 description coverage is 100% and the 'kind' enum is fully documented with routing rules, including the crew_question and referral_lead thresholds. The description's example list parallels that content without adding syntax or format guidance for name/context/requester, so the schema does the heavy lifting.

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 ('Pass a question or request to the owner') and scopes it precisely to cases the fact sheet doesn't cover. This distinguishes it from get_dream_on_facts and the other lookup/booking siblings, which all operate on structured inventory rather than human escalation.

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 the triggering condition explicitly ('when the fact sheet doesn't cover it') plus a concrete enumeration of qualifying cases (holiday pricing, discounts, contract/payment/cancellation terms, longer/shorter stays, special services). The fact-sheet qualifier doubles as a when-not rule, so the agent knows to try the facts tool first.

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

All Dream On Concierge 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