From 5ded947b730081f17bcbb73d8c54462168614c5e Mon Sep 17 00:00:00 2001 From: spencerm Date: Mon, 24 Aug 2026 15:37:16 -0600 Subject: [PATCH] Document include=assets as the way to see a ticket's associated assets The /tickets/{id}/associated-assets path 404s on this instance; assets come back embedded via GET /tickets/{id}?include=assets. Spell out the full include list on get_ticket and in the skill reference so consumers don't hunt for a nonexistent endpoint. Co-Authored-By: Claude Fable 5 --- mcp-server/server.py | 6 +++++- reference.md | 5 +++++ 2 files changed, 10 insertions(+), 1 deletion(-) diff --git a/mcp-server/server.py b/mcp-server/server.py index f867a0a..76fe995 100644 --- a/mcp-server/server.py +++ b/mcp-server/server.py @@ -303,7 +303,11 @@ def list_ticket_statuses() -> str: @mcp.tool() def get_ticket(ticket_id: int, include: str | None = None) -> str: - """Get a ticket by id. `include` e.g. "conversations,requester,stats". + """Get a ticket by id. `include` accepts a comma-separated subset of: + conversations, requester, requested_for, stats, problem, assets, tags, + related_tickets. NOTE: include=assets is the ONLY way to see the ticket's + associated CMDB assets (a /tickets/{id}/associated-assets path does not + exist — it 404s); the assets come back embedded in the ticket object. Numeric enums come back with companion *_label fields (priority_label, status_label, impact_label, urgency_label) — use those names, never guess the scale (priority 4 is Urgent, not low).""" diff --git a/reference.md b/reference.md index 178ad9b..e064161 100644 --- a/reference.md +++ b/reference.md @@ -86,6 +86,11 @@ lists which ones they're in). - `GET /tickets` supports `filter` presets (`new_and_my_open`, `watching`, `spam`, `deleted`), `updated_since`, `order_by`, `order_type`, `page`, `per_page` (max 100), and `include` (`conversations`, `requester`, `stats`). +- `GET /tickets/{id}?include=assets` is the **only** way to see a ticket's + associated CMDB assets — they come back embedded in the ticket object. There + is no `/tickets/{id}/associated-assets` endpoint (it 404s). Other + single-ticket includes: `conversations`, `requester`, `requested_for`, + `stats`, `problem`, `tags`, `related_tickets`. - `GET /tickets/filter?query="..."` is for ad-hoc field queries (also 100/page). ## Pagination & rate limits