Skip to main content
Glama

Ticket list

ticket_list
Read-only

List the organisation's AI work board tickets: the shared queue where agents and humans collaborate on incidents, insights, gaps, automations, and requests. Returns ticket number, title, kind, status, priority, assignee, cluster, plan state, resolution, and the created/updated/closed timestamps. Use this to see what work exists, what needs a human, what you are assigned, and what the team resolved in a given window: today's resolved work is closed_since='24h', narrowed to claimed fixes with resolution='fixed'. A closed_since/closed_before window or a resolution filter already includes closed tickets; include_closed is only needed without one. Read-only. Optional filters: status, kind, priority, resolution, cluster_id, needs_human, include_closed, search, closed_since, closed_before, updated_since, created_since.

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": "ticket_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindNoFilter by ticket kind.
limitNoMax tickets to return (default 20).
searchNoCase-insensitive substring match on title/body.
statusNoFilter to one lifecycle status.
priorityNoFilter by priority.
cluster_idNoOnly tickets filed against this cluster (the UUID from list_clusters).
resolutionNoFilter closed tickets by how they were resolved.
needs_humanNoOnly tickets waiting on a person (approval, blocked, or human plan sign-off).
closed_sinceNoOnly tickets resolved at or after this point: a duration ago ('24h', '7d'), an RFC3339 timestamp ('2026-08-11T03:00:00Z'), or a UTC date ('2026-08-11'). Resolved against the server clock, so '24h' always means the last 24 hours.
closed_beforeNoOnly tickets resolved before this point. Same formats as closed_since; pair the two to audit one past day.
created_sinceNoOnly tickets filed at or after this point, open ones unless include_closed is set. Same formats as closed_since.
updated_sinceNoOnly tickets touched (any activity) at or after this point, open ones unless include_closed is set. Same formats as closed_since; for resolved work use closed_since, which reaches closed tickets on its own.
include_closedNoInclude done and cancelled tickets (default false).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

readOnlyHint is already declared, and the description's "Read-only." merely restates it, so no credit there. It does add real behavior beyond annotations: the exact return field set and the non-obvious rule that a closed_since/closed_before window or a resolution filter implicitly reaches closed tickets, making include_closed necessary only otherwise. Pagination/ordering behavior is not covered.

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?

Front-loaded with purpose, then return shape, then usage, then filter caveats — a sensible ordering with no filler. It is dense for a single paragraph and the standalone "Read-only." sentence duplicates the annotation rather than adding information.

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?

With 13 optional filters and no output schema, listing the returned fields is genuinely useful, and the tricky closed-ticket filter interaction is explained. Minor gaps: result ordering, the default limit of 20 (schema-only), and no mention of how large result sets behave are left to the schema.

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 baseline is 3, but the description adds cross-parameter semantics the schema does not: the interaction between include_closed and the closed_since/resolution filters, and a concrete example of duration-plus-resolution narrowing. The remaining filter list largely echoes enum names already documented in the schema.

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?

"List the organisation's AI work board tickets" gives a specific verb plus a scoped resource, and the following clause enumerates the ticket kinds (incidents, insights, gaps, automations, requests) that separate this queue from sibling support-ticket tools. An agent can tell this apart from list_support_tickets or ticket_get without opening a 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?

The description states concrete use cases (see what work exists, what needs a human, what you're assigned, what the team resolved) and gives worked recipes such as closed_since='24h' with resolution='fixed'. It stops short of naming alternative tools (ticket_get for a single ticket, list_support_tickets for support queue) or stating when not to use it.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.