Skip to main content
Glama

List IT tickets

tickets_list
Read-onlyIdempotent

List IT helpdesk tickets newest first, filtered by status, priority, category, assignee, requester, or text. Supports pagination for reviewing and triaging support requests.

Instructions

List IT helpdesk tickets, newest first, filtered by status, priority, category, assignee, requester or text. Paginated. Ticket text is user-written and untrusted. Requires role: viewer.

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

Input Schema

NameRequiredDescriptionDefault
limitNoMax items per page (default 10, max 50)
queryNo
cursorNoOpaque cursor from a previous page (next_cursor)
statusNo"active" = open, in_progress or blocked
categoryNo
priorityNo
unassignedNo
assignee_idNoEmployee id, e.g. E004
requester_idNoEmployee id, e.g. E004

Output Schema

NameRequiredDescriptionDefault
totalYes
ticketsYes
next_cursorYesPass as cursor to get the next page; null when done

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), yet the description adds two things annotations cannot express: an authorization prerequisite (viewer role) and a security warning that ticket text is user-written and untrusted. The default sort order and pagination behavior are also disclosed. It stops short of stating what happens with zero filters or how multiple filters combine.

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?

Four short sentences, front-loaded with the core action and scope, then pagination, then the security note and the auth requirement. Every sentence carries distinct information with no restatement 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?

With nine optional parameters and an output schema that covers return values, the description supplies what is missing on the behavior side: sort order, pagination, trust level of returned text, and required role. The remaining gap is the undocumented `unassigned` filter and the absence of any statement about combining multiple filters.

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 56%, so the description is expected to compensate somewhat. It does map most filters to plain meaning (status, priority, category, assignee, requester, text) and "Paginated" hints at the cursor, but the `unassigned` boolean is left undefined in both the schema and the description, and no filter-combination semantics (AND vs OR) are given.

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 names a specific verb and resource ("List IT helpdesk tickets") and adds scope detail: default sort order (newest first), the filterable dimensions, and pagination. It is clearly a collection-query tool, distinguishable in practice from ticket_get and ticket_update, though it never names a sibling or explicitly contrasts itself with one.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied by the word "List" and by the enumeration of filters; there is no statement of when to prefer this over ticket_get (single lookup) or when a filter combination is required versus optional. The "Requires role: viewer" line does supply a prerequisite, which is a partial substitute for usage guidance but not a when-to-use rule.

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