Skip to main content
Glama

Ticker: Live Event Ticket Market

by com.findticker
OverviewDiscussionsAdmin

Set Watchlist Defaults

set_watch_defaults
Destructive

Removed: Watch defaults are an account setting. Change them in the Ticker web app under Settings.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
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.
destination_idsNoDestinations a new watch delivers to by default, from list_destinations. An empty array clears them.
notification_modeNoHow a new watch delivers by default: `instant`, `batched` or `muted`. '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. 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."
  2. Changed2 schema fields changed
    • changedInput schema / properties / notification_mode / description
      Previous value: -"How a new watch delivers by default."New value: +"How a new watch delivers by default: `instant`, `batched` or `muted`. '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"
+]
  3. 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"
+}
  4. First observed

TDQS

A4.2/5.0
Behavior4/5

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

The annotations describe an active mutation (readOnlyHint=false, destructiveHint=true, openWorldHint=true), and the description adds the far more important behavioral fact that the capability has been removed — information the structured fields do not carry. It stops short of saying whether invocation errors or silently no-ops, which leaves a minor gap.

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?

A single short sentence, front-loaded with the status change and followed immediately by the redirect. Zero waste; every clause earns its place.

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 removed tool, the description covers what an agent needs: don't call it, use Settings instead. The only omission is the exact behavior on invocation (error vs no-op), which matters somewhat given the annotations still advertise a destructive write.

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 description coverage is 100% and the input schema documents all three parameters (including the nested trigger structure) in detail, so the baseline of 3 applies. The description adds nothing about parameters, but nothing is needed since the tool is removed.

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 opens with 'Removed:' and identifies the resource (watch defaults), making the tool's actual status unambiguous. It doesn't restate what the tool used to do, but for a deprecated endpoint the operative fact — it no longer works — is stated plainly and distinguishes it from the live sibling get_watch_defaults.

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?

It explicitly tells the agent when not to use it and where to go instead ('Change them in the Ticker web app under Settings'). That is a complete when-not plus alternative routing, the strongest form of usage guidance.

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