Skip to main content
Glama

deals

by com.kitsdeals
OverviewDiscussionsAdmin

Register a deal watch

register_watch

Register a standing deal watch. Writes the intent to the sourcing pipeline and returns delivery channels: a one-time token-gated Atom feed plus an optional webhook that activates after interpretation. Progress and live matches are available through check_watch using the returned watch_id. A concrete model_number usually auto-promotes; family intents can require review. conditions defaults to new and open_box.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
specsNoStructured spec/attribute constraints. Omit keys you have no value for. Whole-entry null, empty, none and n/a markers are ignored and counted. Pass these whenever the human names a hard requirement. Keys are generated from docs/spec-keys.json: numeric <spec_key>_min/_max (an exact 8 TB drive is storage_gb_min: 8000 plus storage_gb_max: 8000), enum/list <spec_key>_in for any-of (camera_type_in, bundle_includes_in), enum-list <spec_key>_contains_all for every requested member (bundle_includes_contains_all), and boolean direct keys (bundle). Numeric bounds may use {value,unit} with a registered conversion. Storage uses decimal GB: 1 TB = 1000 GB. Unknown keys are rejected; deals missing the constrained spec are excluded (must-have semantics). Deterministic intent extraction is a fallback; explicit specs always override it, and soft phrasing ("around 65 inches") is never auto-constrained.
intentYesFree-text intent (e.g. "Oura Ring 4 silver under $350"). The interpretation pipeline owns the structuring.
agent_idNoSelf-identifier for telemetry (e.g. "claude-desktop:tom"). Helps us prioritize agent demand.
conditionsNoAccepted deal conditions. Defaults to new + open_box. During consent, surface all four categories and ask whether to add refurbished/pre_owned or restrict to new only.
model_numberNoManufacturer model number (MPN) for the exact variant — e.g. "K-65XR70" for the Sony BRAVIA 7 65". A concrete MPN auto-promotes in ~60s; family-level intents without one require operator review (hours).
max_price_centsNoHard price ceiling for delivery, in cents (a numeric string like "150000" is accepted).
min_discount_pctNoMinimum discount percentage for delivery.
webhook_callback_urlNohttps:// endpoint to receive push deliveries (activates post-interpretation).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / specs / additionalProperties / anyOf
      Previous value: -[
-  {
-    "type": "number"
-  },
-  {
-    "type": "string"
-  },
-  {
-    "type": "boolean"
-  },
-  {
-    "items": {
-      "type": "string"
-    },
-    "type": "array"
-  },
-  {
-    "additionalProperties": false,
-    "properties": {
-      "unit": {
-        "maxLength": 24,
-        "type": "string"
-      },
-      "value": {
-        "type": "number"
-      }
-    },
-    "required": [
-      "value",
-      "unit"
-    ],
-    "type": "object"
-  }
-]New value: +[
+  {
+    "anyOf": [
+      {
+        "type": "number"
+      },
+      {
+        "type": "string"
+      },
+      {
+        "type": "boolean"
+      },
+      {
+        "items": {
+          "type": "string"
+        },
+        "type": "array"
+      },
+      {
+        "additionalProperties": false,
+        "properties": {
+          "unit": {
+            "maxLength": 24,
+            "type": "string"
+          },
+          "value": {
+            "type": "number"
+          }
+        },
+        "required": [
+          "value",
+          "unit"
+        ],
+        "type": "object"
+      }
+    ]
+  },
+  {
+    "type": "null"
+  }
+]
    • changedInput schema / properties / specs / description
      Previous value: -"Structured spec/attribute constraints. Pass these whenever the human names a hard requirement. Keys are generated from docs/spec-keys.json: numeric <spec_key>_min/_max (an exact 8 TB drive is storage_gb_min: 8000 plus storage_gb_max: 8000), enum/list <spec_key>_in for any-of (camera_type_in, bundle_includes_in), enum-list <spec_key>_contains_all for every requested member (bundle_includes_contains_all), and boolean direct keys (bundle). Numeric bounds may use {value,unit} with a registered conversion. Storage uses decimal GB: 1 TB = 1000 GB. Unknown keys are rejected; deals missing the constrained spec are excluded (must-have semantics). Deterministic intent extraction is a fallback; explicit specs always override it, and soft phrasing (\"around 65 inches\") is never auto-constrained."New value: +"Structured spec/attribute constraints. Omit keys you have no value for. Whole-entry null, empty, none and n/a markers are ignored and counted. Pass these whenever the human names a hard requirement. Keys are generated from docs/spec-keys.json: numeric <spec_key>_min/_max (an exact 8 TB drive is storage_gb_min: 8000 plus storage_gb_max: 8000), enum/list <spec_key>_in for any-of (camera_type_in, bundle_includes_in), enum-list <spec_key>_contains_all for every requested member (bundle_includes_contains_all), and boolean direct keys (bundle). Numeric bounds may use {value,unit} with a registered conversion. Storage uses decimal GB: 1 TB = 1000 GB. Unknown keys are rejected; deals missing the constrained spec are excluded (must-have semantics). Deterministic intent extraction is a fallback; explicit specs always override it, and soft phrasing (\"around 65 inches\") is never auto-constrained."
  2. Changed2 schema fields changed
    • changedInput schema / properties / specs / additionalProperties / anyOf
      Previous value: -[
-  {
-    "type": "number"
-  },
-  {
-    "type": "string"
-  },
-  {
-    "type": "boolean"
-  },
-  {
-    "items": {
-      "type": "string"
-    },
-    "type": "array"
-  }
-]New value: +[
+  {
+    "type": "number"
+  },
+  {
+    "type": "string"
+  },
+  {
+    "type": "boolean"
+  },
+  {
+    "items": {
+      "type": "string"
+    },
+    "type": "array"
+  },
+  {
+    "additionalProperties": false,
+    "properties": {
+      "unit": {
+        "maxLength": 24,
+        "type": "string"
+      },
+      "value": {
+        "type": "number"
+      }
+    },
+    "required": [
+      "value",
+      "unit"
+    ],
+    "type": "object"
+  }
+]
    • changedInput schema / properties / specs / description
      Previous value: -"Structured spec/attribute constraints. Pass these whenever the human names a hard requirement. Keys are generated from docs/spec-keys.json: numeric <spec_key>_min/_max (an exact 8 TB drive is storage_gb_min: 8000 plus storage_gb_max: 8000), enum/list <spec_key>_in (camera_type_in, bundle_includes_in), and boolean direct keys (bundle). Storage uses decimal GB: 1 TB = 1000 GB. Unknown keys are rejected; deals missing the constrained spec are excluded (must-have semantics). Deterministic intent extraction is a fallback; explicit specs always override it, and soft phrasing (\"around 65 inches\") is never auto-constrained."New value: +"Structured spec/attribute constraints. Pass these whenever the human names a hard requirement. Keys are generated from docs/spec-keys.json: numeric <spec_key>_min/_max (an exact 8 TB drive is storage_gb_min: 8000 plus storage_gb_max: 8000), enum/list <spec_key>_in for any-of (camera_type_in, bundle_includes_in), enum-list <spec_key>_contains_all for every requested member (bundle_includes_contains_all), and boolean direct keys (bundle). Numeric bounds may use {value,unit} with a registered conversion. Storage uses decimal GB: 1 TB = 1000 GB. Unknown keys are rejected; deals missing the constrained spec are excluded (must-have semantics). Deterministic intent extraction is a fallback; explicit specs always override it, and soft phrasing (\"around 65 inches\") is never auto-constrained."
  3. Changed1 schema field changed
    • changedInput schema / properties / specs / description
      Previous value: -"Structured spec/attribute constraints. Keys are generated from docs/spec-keys.json: numeric <spec_key>_min/_max (size_inches_min), enum/list <spec_key>_in (camera_type_in, bundle_includes_in), and boolean direct keys (bundle). Example: { \"size_inches_min\": 65, \"camera_type_in\": [\"dslr\"], \"bundle\": true }. Unknown keys are rejected; deals missing the constrained spec are excluded (must-have semantics). If you skip this, explicit numeric thresholds in the intent text (\"at least 65 inches\", \"16GB RAM or more\") are extracted automatically at interpretation — your explicit specs always override extraction; soft phrasing (\"around 65 inches\") is never auto-constrained."New value: +"Structured spec/attribute constraints. Pass these whenever the human names a hard requirement. Keys are generated from docs/spec-keys.json: numeric <spec_key>_min/_max (an exact 8 TB drive is storage_gb_min: 8000 plus storage_gb_max: 8000), enum/list <spec_key>_in (camera_type_in, bundle_includes_in), and boolean direct keys (bundle). Storage uses decimal GB: 1 TB = 1000 GB. Unknown keys are rejected; deals missing the constrained spec are excluded (must-have semantics). Deterministic intent extraction is a fallback; explicit specs always override it, and soft phrasing (\"around 65 inches\") is never auto-constrained."
  4. Changed1 schema field changed
    • changedInput schema / properties / conditions / description
      Previous value: -"Accepted deal conditions. Defaults to new-only unless explicit condition acceptance is present in intent text."New value: +"Accepted deal conditions. Defaults to new + open_box. During consent, surface all four categories and ask whether to add refurbished/pre_owned or restrict to new only."
  5. Changed1 schema field changed
    • addedInput schema / properties / conditions
      Added value: +{
+  "description": "Accepted deal conditions. Defaults to new-only unless explicit condition acceptance is present in intent text.",
+  "items": {
+    "enum": [
+      "new",
+      "open_box",
+      "refurbished",
+      "pre_owned"
+    ],
+    "type": "string"
+  },
+  "minItems": 1,
+  "type": "array"
+}
  6. Changed1 schema field changed
    • removedInput schema / properties / user_email
      Removed value: -{
-  "description": "Email address for deal alerts (a double-opt-in confirmation is sent first).",
-  "maxLength": 200,
-  "type": "string"
-}
  7. Changed3 schema fields changed
    • changedInput schema / properties / intent / description
      Previous value: -"Free-text intent, exactly as your human expressed it (e.g. \"Oura Ring 4 silver under $350\"). Our interpretation pipeline owns the structuring."New value: +"Free-text intent (e.g. \"Oura Ring 4 silver under $350\"). The interpretation pipeline owns the structuring."
    • changedInput schema / properties / model_number / description
      Previous value: -"Manufacturer model number (MPN) when you know the exact variant — e.g. \"K-65XR70\" for the Sony BRAVIA 7 65\". IMPORTANT: family-level intents (\"Sony BRAVIA 7\") without a concrete variant require operator review and can take hours; a concrete MPN auto-promotes in ~60s. If you know the family but not the MPN, ask your human or look it up before registering."New value: +"Manufacturer model number (MPN) for the exact variant — e.g. \"K-65XR70\" for the Sony BRAVIA 7 65\". A concrete MPN auto-promotes in ~60s; family-level intents without one require operator review (hours)."
    • changedInput schema / properties / user_email / description
      Previous value: -"Your human's email for deal alerts (we send a double-opt-in confirmation first)."New value: +"Email address for deal alerts (a double-opt-in confirmation is sent first)."
  8. First observed

TDQS

A3.9/5.0
Behavior4/5

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

All annotations are false (no positive hints), so the description carries the full disclosure burden. It adds meaningful behavioral context: the operation writes/mutates the pipeline, the delivery channels are one-time token-gated with webhook activation post-interpretation, concrete model_number auto-promotes in ~60s while family intents require operator review (hours), and conditions defaults to new/open_box. No contradiction with annotations — 'Writes' aligns with readOnlyHint=false.

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

Conciseness4/5

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

Four sentences, roughly 60 words, with the primary purpose front-loaded and zero filler. Each sentence earns its place: purpose, return channels, sibling routing, promotion behavior, and defaults. It's efficient without being under-specified — appropriately sized for an 8-parameter 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?

For an 8-param tool with no output schema, the description covers the key return values (watch_id, delivery channels) and behavioral expectations (timing, review, defaults). The complex specs parameter is fully documented in the schema, so the description need not repeat it. Minor gaps exist — no failure/error case disclosure — but for a complex tool with a rich schema, the description complements it well.

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%, so the schema documents all 8 parameters thoroughly (especially specs with its extensive key-format explanation). The description largely echoes what the schema already states — model_number auto-promotion timing appears in the schema property description, and conditions default is documented there too. The description's added value is limited to contextual framing (delivery channels) rather than new parameter semantics, so a baseline 3 is appropriate.

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 description states a specific verb+resource ('Register a standing deal watch') and precisely what it does: writes intent to the sourcing pipeline and returns delivery channels (token-gated Atom feed plus optional webhook). It also distinguishes itself by naming the standing/ongoing nature, which separates it from one-time search tools, and explicitly references the check_watch sibling for follow-up, making the tool's role in the family clear.

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?

The description routes the agent to check_watch for progress and live matches using the returned watch_id, which is useful follow-up guidance. However, it never explicitly states when to prefer register_watch over search_deals or latest_deals (standing watch vs one-time query). The standing nature implies the use case, but there's no explicit when-to-use/when-not-to-use guidance or named alternatives for the main competing sibling.

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

All deals 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