Skip to main content
Glama

haggl_hotel_cashback_claim

After the user booked the hotel whose agent's offer they accepted, before its reference code expired: claim the cashback with the hotel's booking confirmation email, exactly as received. Show the user these conditions first, and call this only if they agree: "haggl.ai (MOOJO.ID, INC.) pays cashback on stays at independent and boutique hotels in San Francisco booked while your quote holds (72 hours), for a stay starting within 60 days. Your rate depends on the trips to San Francisco you prove with signed flight or hotel emails from the last 12 months. Booking on the hotel's own site pays the full rate; booking through a travel site pays half. One booking per person. Your agent sends us the hotel's booking confirmation email as the hotel sent it, then, after you check out, the hotel's receipt or thank-you email; we check their signatures and read the hotel, dates, total and trips from them with an AI model, and keep those and fingerprints of the emails, not the emails. We pay within 2 business days of the post-stay email, to the email address you give, by bank transfer through Stripe (Stripe emails you a secure link to enter your bank details) or by PayPal; we delete that address 6 months later. Cancelled stays aren't paid. We may refuse a claim that looks fraudulent, and the offer ends when its budget is spent. Privacy policy: https://www.haggl.ai/privacy." Send terms_version "2026-10-29.2", statement (their words of agreement, quoted, without names or contact details) and payout_email: their email address for the payout, where haggl.ai sends the cashback after the stay (by bank transfer through Stripe, which emails them a link to enter bank details, or by PayPal).

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": {
      "haggl_id": "<haggl_id>",
      "raw_mime_b64": "<raw_mime_b64>",
      "terms_version": "<terms_version>",
      "statement": "<statement>",
      "payout_email": "<payout_email>"
    },
    "name": "haggl_hotel_cashback_claim"
  }
}

Input Schema

NameRequiredDescriptionDefault
channelNoHow the user agreed: in this conversation (default), or in standing instructions.
haggl_idYesThe user's haggl ID.
statementYesThe user's words of agreement, quoted; no names, emails or phone numbers.
payout_emailYesThe user's email address for the payout.
raw_mime_b64YesBase64 (standard or url-safe) of the original email, byte for byte (Gmail format=RAW, or Show original → Download original).
terms_versionYes"2026-10-29.2".

Output Schema

NameRequiredDescriptionDefault
codeNoPresent only when the call failed: a machine-readable error code, e.g. quote_uncertain or rate_limited.
nextNoWhat to do next.
claimNoA hotel cashback claim.
errorNoPresent only when the call failed: what went wrong.
termsNoWhen terms_required: the terms to show the traveler.
recoveryNoWhen the outcome is uncertain: the tool and session_id to read before retrying.
retryableNoWhether the same call may be retried.
status_urlNoWhere the claim can be read again.
retry_after_secondsNoWhen rate limited: seconds to wait before retrying.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior5/5

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

Goes well beyond the annotations (which only declare non-read-only, non-destructive, closed-world, non-idempotent): discloses that the raw email is parsed by an AI model, that fingerprints and extracted fields are retained rather than the email, that payout happens within 2 business days post-stay via Stripe/PayPal, that the email address is deleted after 6 months, and that fraudulent claims or exhausted budgets can be refused.

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 operative instruction is correctly front-loaded, but roughly two-thirds of the text is verbatim legal/terms copy plus a privacy URL. That block is functionally motivated (the agent must show it to the user) yet makes the description long and hard to scan for the actual call contract.

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

Completeness5/5

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

With 6 parameters (5 required), full schema coverage, an output schema, and rich annotations, the description supplies everything else an agent needs: eligibility, timing, consent gating, what to pass verbatim, what happens after submission, and how payment is delivered.

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 baseline is 3, but the description adds real meaning: it prescribes the literal terms_version string, defines statement as the user's own quoted words without names or contact details, and explains payout_email as the destination for a Stripe bank-transfer link or PayPal payment after the stay.

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?

Starts with a specific verb and resource: claim the cashback, with the triggering object (the hotel's booking confirmation email, exactly as received). Preconditions (booked the accepted-offer hotel, before reference code expiry) make it clearly distinct from the sibling reads (haggl_hotel_cashback_get) and writes (haggl_hotel_cashback_add_trip, _stay), though no sibling is named explicitly.

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?

States the exact window in which to call (after booking, before the reference code expires), the prerequisite (the user accepted the agent's offer), and an explicit gate: show the user these conditions first and call only if they agree. It also front-loads the sequence constraint, so the agent knows not to fire this pre-booking.

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