Skip to main content
Glama

Send booking enquiry

send_inquiry

Email a booking inquiry to hello@weewilds.com on behalf of a guest.

Requires an access token (Authorization: Bearer header). Without one this
tool sends nothing and returns the direct booking URL instead — send the
guest there, or to hello@weewilds.com.

Does NOT create an OwnerRez booking directly — the host will reply to the
guest_email to confirm availability and arrange payment. Rate-limited to
5 inquiries per hour per client.

Args:
    unit: One of "muckle-meadow-pod", "cosie-coorie-pod", "bb".
    check_in: Arrival date YYYY-MM-DD.
    check_out: Departure date YYYY-MM-DD, must be after check_in.
    guest_name: Guest's full name.
    guest_email: Valid email — the host replies here.
    guests: Number of guests (1–10).
    notes: Optional special requests (dietary, arrival time, etc.).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "unit": "<unit>",
      "check_in": "<check_in>",
      "check_out": "<check_out>",
      "guest_name": "<guest_name>",
      "guest_email": "<guest_email>",
      "guests": "<guests>"
    },
    "name": "send_inquiry"
  }
}

Input Schema

NameRequiredDescriptionDefault
unitYesWhich WEE WiLDS unit: "muckle-meadow-pod" (Muckle Meadow Glamping Pod), "cosie-coorie-pod" (Cosy Coorie Pod) or "bb" (the B&B, all 4 rooms).
notesNoOptional special requests, e.g. dietary needs or arrival time.
guestsYesNumber of guests, 1 to 10.
check_inYesArrival date, YYYY-MM-DD. Must not be in the past.
check_outYesDeparture date, YYYY-MM-DD. Must be after check_in.
guest_nameYesGuest's full name.
guest_emailYesGuest's email address. The host replies here to confirm and arrange payment.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed10 schema fields changed
    • addedInput schema / properties / check_in / description
      Added value: +"Arrival date, YYYY-MM-DD. Must not be in the past."
    • addedInput schema / properties / check_in / examples
      Added value: +[
      +  "2027-06-14"
      +]
    • addedInput schema / properties / check_out / description
      Added value: +"Departure date, YYYY-MM-DD. Must be after check_in."
    • addedInput schema / properties / check_out / examples
      Added value: +[
      +  "2027-06-17"
      +]
    • addedInput schema / properties / guest_email / description
      Added value: +"Guest's email address. The host replies here to confirm and arrange payment."
    • addedInput schema / properties / guest_name / description
      Added value: +"Guest's full name."
    • addedInput schema / properties / guests / description
      Added value: +"Number of guests, 1 to 10."
    • addedInput schema / properties / notes / description
      Added value: +"Optional special requests, e.g. dietary needs or arrival time."
    • addedInput schema / properties / unit / description
      Added value: +"Which WEE WiLDS unit: \"muckle-meadow-pod\" (Muckle Meadow Glamping Pod), \"cosie-coorie-pod\" (Cosy Coorie Pod) or \"bb\" (the B&B, all 4 rooms)."
    • addedInput schema / properties / unit / enum
      Added value: +[
      +  "muckle-meadow-pod",
      +  "cosie-coorie-pod",
      +  "bb"
      +]
  2. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Adds substantial context beyond the annotations: a hard rate limit of 5 inquiries per hour per client, the Bearer-token requirement, and the specific fallback behavior when unauthenticated. It also clarifies downstream flow (host replies to guest_email). It does not describe success return values, though the annotations already mark this as non-read-only, open-world, non-idempotent, and non-destructive.

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?

Front-loads the action, then the auth/fallback caveat, then the non-booking clarification, then a compact Args block. Every sentence carries operational information and nothing is buried mid-paragraph.

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?

Covers preconditions, rate limits, and failure behavior thoroughly, but says nothing about what a successful call returns (and no output schema exists), leaving the success response opaque to the agent.

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; the description reinforces the key semantics without contradicting the schema, notably that guest_email is the reply channel and check_out must follow check_in. It largely restates schema content rather than adding new constraints, so it stays near the baseline.

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 ("Email a booking inquiry to hello@weewilds.com on behalf of a guest") and explicitly delimits what it does not do ("Does NOT create an OwnerRez booking directly"). This cleanly separates it from the read-only siblings get_availability, get_pricing, and get_unit_details.

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?

Gives clear conditions for use, including the no-token fallback ("send the guest there, or to hello@weewilds.com") and the note that the host confirms later. It does not explicitly route the agent to check availability or pricing first, so the alternative-tool guidance is incomplete.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources