haggl.ai

haggl_get_my_offers

Read-onlyIdempotent

Read what haggl.ai holds for the user's haggl ID: when it was created and the negotiations, offers and codes linked to it, newest first.

Input Schema

Name	Required	Description	Default
`haggl_id`	Yes	The user's haggl ID.

Output Schema

Name	Required	Description
`code`	No	Present only when the call failed: a machine-readable error code, e.g. quote_uncertain or rate_limited.
`error`	No	Present only when the call failed: what went wrong.
`offers`	No	Negotiations linked to this haggl ID, newest first.
`record`	No	What the record holds: verified purchases by category and offer counts.
`consent`	No	The consent on record: version, time and channel.
`recovery`	No	When the outcome is uncertain: the tool and session_id to read before retrying.
`retryable`	No	Whether the same call may be retried.
`created_at`	No	ISO 8601 time the haggl ID was created.
`last_used_at`	No	ISO 8601 time it was last used.
`cashback_claims`	No	The user's haggl.ai cashback claims, newest first, when they have any. For a ready or paid claim, haggl_get_cashback returns its payout_url.
`cashback_quotes`	No	The user's cashback rates that still hold, the latest per store, when they have any: an order placed there before valid_until gets the rate.
`retry_after_seconds`	No	When rate limited: seconds to wait before retrying.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 29, 2026

changedOutput schema / properties / cashback_quotes / items / properties / algorithmic_price_disclosure / description

Previous value: -"Show word for word, next to the rate."New value: +"For a user in New York: show word for word, next to the rate."

changedOutput schema / properties / offers / items / properties / algorithmic_price_disclosure / description

Previous value: -"With a discount: show word for word, next to the discount."New value: +"With a discount, for a user in New York: show word for word, next to the discount."

Changed2 schema fields changedOct 19, 2026

addedOutput schema / properties / offers / items / properties / algorithmic_price_disclosure

Added value: +{
+  "description": "With a discount: show word for word, next to the discount.",
+  "type": "string"
+}

addedOutput schema / properties / offers / items / properties / personalized_price_notice

Added value: +{
+  "description": "With a discount: show word for word, next to the discount.",
+  "type": "string"
+}

Changed1 schema field changedOct 19, 2026
- addedOutput schema / properties / cashback_quotes / items / properties / algorithmic_price_disclosure
```
Added value: +{
+  "description": "Show word for word, next to the rate.",
+  "type": "string"
+}
```

Changed1 schema field changedOct 18, 2026

addedOutput schema / properties / cashback_quotes

Added value: +{
+  "description": "The user's cashback rates that still hold, the latest per store, when they have any: an order placed there before valid_until gets the rate.",
+  "items": {
+    "description": "A cashback quote.",
+    "properties": {
+      "personalized_price_notice": {
+        "description": "Show word for word.",
+        "type": "string"
+      },
+      "quote_id": {
+        "description": "Quote id.",
+        "type": "string"
+      },
+      "rate_pct": {
+        "description": "Cashback rate, in percent of the order total.",
+        "type": "number"
+      },
+      "store": {
+        "description": "The store.",
+        "type": "string"
+      },
+      "valid_until": {
+        "description": "ISO 8601 time the rate holds until.",
+        "type": "string"
+      }
+    },
+    "type": "object"
+  },
+  "type": "array"
+}

Changed1 schema field changedOct 18, 2026

addedOutput schema / properties / cashback_claims

Added value: +{
+  "description": "The user's haggl.ai cashback claims, newest first, when they have any. For a ready or paid claim, haggl_get_cashback returns its payout_url.",
+  "items": {
+    "description": "A cashback claim.",
+    "properties": {
+      "cashback": {
+        "description": "What haggl.ai pays back.",
+        "properties": {
+          "amount": {
+            "description": "Amount and currency.",
+            "type": "string"
+          },
+          "rate_pct": {
+            "description": "Share of the order total, in percent.",
+            "type": "number"
+          }
+        },
+        "type": "object"
+      },
+      "claim_id": {
+        "description": "Claim id for haggl_get_cashback.",
+        "type": "string"
+      },
+      "payout_available_at": {
+        "description": "ISO 8601 time the payout opens, while pending.",
+        "type": "string"
+      },
+      "status": {
+        "description": "pending (held until payout_available_at), ready (the payout can be issued) or paid.",
+        "type": "string"
+      },
+      "store": {
+        "description": "The store the order was at.",
+        "type": "string"
+      }
+    },
+    "type": "object"
+  },
+  "type": "array"
+}

First observedOct 16, 2026

TDQS

A3.6/5.0

Behavior3/5

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

Annotations already declare the safe read-only, idempotent, non-destructive profile, so the description does not need to repeat those. It adds useful context by listing what is returned and the 'newest first' ordering, but it omits auth requirements, error behavior, or result limits.

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?

The definition is a single well-formed sentence with no wasted words. It front-loads the action and scope, then lists the returned data and ordering.

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?

For a low-complexity read tool with full schema coverage, rich annotations, and an output schema, the description is sufficiently complete. It explains the data domain and ordering, though it does not cover edge cases such as invalid or missing haggl IDs.

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 coverage is 100% and the single parameter has its own description ('The user's haggl ID'). The tool description restates the haggl ID scope but adds no format, syntax, or validation detail beyond what the schema provides, so the baseline 3 applies.

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 uses a clear verb ('Read') and specifies the resource: data held for the user's haggl ID, including creation time, negotiations, offers, and codes. It is understandable without opening the schema, but it does not explicitly distinguish this tool from siblings like haggl_get_negotiation or haggl_get_bids.

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

Usage Guidelines3/5

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

Usage is implied by the scope ('for the user's haggl ID'), but there is no explicit when-to-use guidance, no exclusions, and no named alternatives. An agent can infer this is for retrieving stored account data, but must reason about sibling tools on its own.

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

All haggl.ai tools Inspect

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

Need Help?