Ticker: Live Event Ticket Market

List Watched Events

list_watchlist

Read-only

Lists the events the account watches, with current prices, armed triggers, alert counts and alerts_live. Watches of events that ended over a week ago are left out unless include_archived is true. Use it when the person asks which events they watch. For saved Views, use list_views.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_watchlist"
  }
}

Input Schema

Name	Required	Description	Default
`page`	No	The page to read, from 1. Default 1.
`sort`	No	The order of the list: created_at (default, when the event was starred), utc_date (the event's date), last_matched_at (the latest alert) or event_name.	created_at
`limit`	No	Watched events per page. Default 50, at most 100.
`order`	No	desc (default) or asc.	desc
`search`	No	Filter by event name.
`archived`	No	Stars whose event finished more than a week ago: exclude (default) leaves them out, include adds them, only reads them. true means only, false means exclude.	exclude
`include_archived`	No	Also return watches archived because their event finished more than a week ago.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 4, 2026

addedInput schema / properties / archived

Added value: +{
+  "default": "exclude",
+  "description": "Stars whose event finished more than a week ago: exclude (default) leaves them out, include adds them, only reads them. true means only, false means exclude.",
+  "enum": [
+    "exclude",
+    "include",
+    "only",
+    "true",
+    "false"
+  ],
+  "type": "string"
+}

Changed4 schema fields changedNov 2, 2026

addedInput schema / properties / limit / description

Added value: +"Watched events per page. Default 50, at most 100."

addedInput schema / properties / order / description
```
Added value: +"desc (default) or asc."
```

addedInput schema / properties / page / description

Added value: +"The page to read, from 1. Default 1."

addedInput schema / properties / sort / description

Added value: +"The order of the list: created_at (default, when the event was starred), utc_date (the event's date), last_matched_at (the latest alert) or event_name."

Changed1 schema field changedOct 10, 2026
- removedInput schema / properties / limit / maximum
```
Removed value: -100
```
First observedOct 2, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already establish the safe read profile (readOnlyHint=true, destructiveHint=false, openWorldHint=false), so the description's job is to add what annotations cannot. It does that by disclosing a non-obvious default filter: watches whose event ended over a week ago are silently omitted unless include_archived is true. It does not explain pagination behavior or what the alert/trigger fields look like, but the default-exclusion disclosure is the genuinely valuable part.

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?

Three short sentences, front-loaded with what the tool returns, followed by the non-obvious filtering default, then routing. No filler and no repetition of the title or annotations.

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?

A read-only list tool with no output schema needs its payload described, and the description does that. The archived default is covered, but the overlapping archived/include_archived parameters at 7 total parameters leave a small gap in completeness.

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 every parameter including the archived enum and sort options is already documented, which sets the baseline at 3. The description adds meaning only for include_archived, restating its default exclusion behavior. It notably does not explain how the 'archived' enum parameter (include/only/exclude/true/false) relates to the 'include_archived' boolean, a real ambiguity given both exist.

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 and resource ('Lists the events the account watches') and goes further by enumerating the returned payload fields (current prices, armed triggers, alert counts, alerts_live). It also explicitly separates itself from list_views, which is the nearest confusable sibling.

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?

Gives an explicit invocation condition ('Use it when the person asks which events they watch') and an explicit alternative plus the condition that selects it ('For saved Views, use list_views'). The only real alternative for this data shape is covered, so nothing is left to inference.

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 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?