Skip to main content
Glama
Sign In

Ticker: Live Event Ticket Market

by com.findticker
OverviewDiscussionsAdmin

Watch Event and Set Alerts

watch_event
Destructive

Stars one event and turns on its alerts, or changes the triggers or email mode of an event already starred; only what you pass changes, and the triggers input lists each trigger and its range. Use it when the person asks to watch one event or to be alerted about it. The plan sets how many starred events alert at once, the newest first; dormanted lists the events this star stopped alerting. For alerts on every event that meets a predicate, use create_view.

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": {
      "event_id": "<event_id>"
    },
    "name": "watch_event"
  }
}

Input Schema

NameRequiredDescriptionDefault
event_idYesEvent to watch (from search_events or screen_events).
triggersNoPer-event trigger settings, e.g. {"price_z":{"enabled":true,"params":{"threshold":2.5}}}. Each key says what it alerts on and the range of its params. Omit to use the saved defaults. A value outside its range is refused with an error naming the field and its min and max, and nothing is written.
notification_modeNo`instant` = email each alert as it happens (default); `batched` = the alerts go out together in one email; `muted` = record alerts without sending them. 'digest' is the old name of 'batched', accepted until 2026-11-30 and stored as 'batched'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / triggers / properties / absorption / description
      Previous value: -"Tickets leaving fast: A large share of the listed tickets leaves the marketplace. Off by default. Measures listings that disappear, which is not the same as confirmed sales. params: threshold 0.3 to 0.9 (default 0.5)."New value: +"Tickets leaving fast: A large share of the listed tickets leaves the marketplace. Off by default. Counts the tickets that leave the marketplace, bought, withdrawn or expired. params: threshold 0.3 to 0.9 (default 0.5)."
    • changedInput schema / properties / triggers / properties / demand / description
      Previous value: -"Demand spike: Fires when Interest in this event, the most people viewing in an hour, rises by this many people versus the day before. Off by default. A change in Interest from one date to the next, not a z-score. Coverage is still filling in, so quiet events may never trigger it. params: threshold 1 to 50 (default 5)."New value: +"Demand spike: Fires when Interest in this event, the most people viewing in an hour, rises by this many people versus the day before. Off by default. A change in Interest from one date to the next, not a z-score. params: threshold 1 to 50 (default 5)."
  2. Changed1 schema field changed
    • changedInput schema / properties / triggers / properties / demand / description
      Previous value: -"Demand spike: Fires when Interest in this event, people viewing per hour, rises by this much versus the day before. Off by default. A change in Interest per hour from one date to the next, not a z-score. Coverage is still filling in, so quiet events may never trigger it. params: threshold 0.1 to 5 (default 0.2)."New value: +"Demand spike: Fires when Interest in this event, the most people viewing in an hour, rises by this many people versus the day before. Off by default. A change in Interest from one date to the next, not a z-score. Coverage is still filling in, so quiet events may never trigger it. params: threshold 1 to 50 (default 5)."
  3. Changed1 schema field changed
    • changedInput schema / properties / triggers / properties / demand / description
      Previous value: -"Demand spike: Interest in this event's listings rises versus the day before. Off by default. A change in Interest from one date to the next, not a z-score. Coverage is still filling in, so quiet events may never trigger it. params: threshold 1 to 50 (default 5)."New value: +"Demand spike: Fires when Interest in this event, people viewing per hour, rises by this much versus the day before. Off by default. A change in Interest per hour from one date to the next, not a z-score. Coverage is still filling in, so quiet events may never trigger it. params: threshold 0.1 to 5 (default 0.2)."
  4. Changed7 schema fields changed
    • changedInput schema / properties / triggers / description
      Previous value: -"Per-event trigger overrides, e.g. {\"price_z\":{\"enabled\":true,\"params\":{\"threshold\":2.5}}}. Omit to use your saved defaults. A value outside its range in list_watch_triggers is refused with an error naming the field and its min and max, and nothing is written."New value: +"Per-event trigger settings, e.g. {\"price_z\":{\"enabled\":true,\"params\":{\"threshold\":2.5}}}. Each key says what it alerts on and the range of its params. Omit to use the saved defaults. A value outside its range is refused with an error naming the field and its min and max, and nothing is written."
    • addedInput schema / properties / triggers / properties / absorption / description
      Added value: +"Tickets leaving fast: A large share of the listed tickets leaves the marketplace. Off by default. Measures listings that disappear, which is not the same as confirmed sales. params: threshold 0.3 to 0.9 (default 0.5)."
    • addedInput schema / properties / triggers / properties / demand / description
      Added value: +"Demand spike: Interest in this event's listings rises versus the day before. Off by default. A change in Interest from one date to the next, not a z-score. Coverage is still filling in, so quiet events may never trigger it. params: threshold 1 to 50 (default 5)."
    • addedInput schema / properties / triggers / properties / lifecycle / description
      Added value: +"On-sale, presale, event week, low inventory: Fires when an on-sale or presale is announced, event week begins, or listed inventory runs low. On by default. params: event_week_days 1 to 30  days out (default 7); low_inventory_percent 1 to 50 % (default 10)."
    • addedInput schema / properties / triggers / properties / pct_move / description
      Added value: +"Price % move: The price changes by more than this percentage. Off by default. params: metric lowest | median (default lowest); window 1d | 7d (default 1d); threshold 5 to 100 % (default 15)."
    • addedInput schema / properties / triggers / properties / price_z / description
      Added value: +"Unusual price move: Fires when the 7-day price move is at least 2× this event's own normal swing, in either direction. On by default. params: threshold 1 to 5 (default 2)."
    • addedInput schema / properties / triggers / properties / weather / description
      Added value: +"Weather: Fires when the forecast for the event turns bad, and again when it clears. On by default."
  5. Changed2 schema fields changed
    • changedInput schema / properties / notification_mode / description
      Previous value: -"`instant` = email each alert as it happens (default); `digest` = the alerts go out together in one email; `muted` = record alerts without sending them."New value: +"`instant` = email each alert as it happens (default); `batched` = the alerts go out together in one email; `muted` = record alerts without sending them. 'digest' is the old name of 'batched', accepted until 2026-11-30 and stored as 'batched'."
    • changedInput schema / properties / notification_mode / enum
      Previous value: -[
-  "instant",
-  "digest",
-  "muted"
-]New value: +[
+  "instant",
+  "batched",
+  "muted",
+  "digest"
+]
  6. Changed1 schema field changed
    • addedInput schema / properties / triggers / properties / weather
      Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "enabled": {
+      "type": "boolean"
+    },
+    "params": {
+      "additionalProperties": {
+        "type": [
+          "number",
+          "string"
+        ]
+      },
+      "type": "object"
+    }
+  },
+  "type": "object"
+}
  7. Changed1 schema field changed
    • changedInput schema / properties / notification_mode / description
      Previous value: -"`instant` = email each alert as it happens (default); `digest` = the alerts go out together in one daily email; `muted` = record alerts without sending them."New value: +"`instant` = email each alert as it happens (default); `digest` = the alerts go out together in one email; `muted` = record alerts without sending them."
  8. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false and destructiveHint=true, so the description's job is to explain the mutation surface — and it does: patch semantics ('only what you pass changes'), omission falling back to saved defaults, atomic validation ('nothing is written' on out-of-range), and a plan-level cap on how many starred events alert at once. The gap is that it never says what happens when the cap is reached (whether an older star silently stops alerting), which is exactly the destructive behavior implied by the hint.

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 core purpose is front-loaded and the create_view routing closes cleanly, but the middle sentence is dense and partly opaque — 'the plan sets how many starred events alert at once, the newest first; dormanted lists the events this star stopped alerting' introduces an undefined term and an unclear response field, which costs more than it earns.

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 tool with a deeply nested triggers object, no output schema and a destructive mutation hint, the description covers the essentials: patch behavior, defaults, error/atomicity, and capacity limits. What's missing is the consequence of exceeding the plan cap and any note on permissions or plan requirements for enabling alerts.

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 earns above that by explaining merge semantics ('only what you pass changes'), that omitting triggers uses saved defaults, and that each trigger key names its own param range with a refused-with-error contract. It adds little about event_id or the enum values of notification_mode beyond what the schema already documents.

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+resource pair ('Stars one event and turns on its alerts') plus the update variant ('changes the triggers or email mode of an event already starred'), and explicitly routes predicate-based alerting to the sibling create_view. An agent can distinguish this from create_view, update_view and unwatch_event without opening any schema.

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 a clear triggering condition ('Use it when the person asks to watch one event or to be alerted about it') and names the key alternative (create_view) with the condition that selects it. It does not mention unwatch_event for the inverse operation, nor does it state when to leave the star untouched.

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

All Ticker: Live Event Ticket Market 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