Support Ticket Triage MCP

Overview Schema Source Related Servers Discussions Admin

list_tickets

Read-onlyIdempotent

Filter and page through support tickets by status, priority, team, category, or SLA state to locate items needing triage.

Instructions

Filter and page through the local support ticket queue.

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_tickets"
  }
}

Input Schema

Name	Required	Description	Default
`asOf`	No
`team`	No
`limit`	No
`offset`	No
`status`	No
`category`	No
`priority`	No
`slaState`	No

Output Schema

Name	Required	Description	Default
`items`	Yes
`limit`	Yes
`total`	Yes
`offset`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 11, 2026

TDQS

B3.1/5.0

Behavior3/5

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

Annotations already declare the tool read-only and non-destructive, so the description need not repeat that. It adds the 'local' qualifier and pagination hint, but lacks deeper behavioral context like default sort order or handling of missing filters. No contradiction with annotations.

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?

A single, front-loaded sentence with no wasted words. It is concise and direct, though somewhat under-specified given the tool's parameter count.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With 8 optional parameters and a rich set of filter enums, the description is too brief. It gives only a high-level summary and does not cover the variety of filtering dimensions (status, priority, team, etc.). An output schema exists, which reduces the need to describe return values, but the description still lacks essential context for a complex listing tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, and the description does not explain any of the 8 parameters. It generically says 'filter' which hints at the filter parameters, but does not add meaning beyond their raw names and enums. The description fails to compensate for the lack of schema descriptions.

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 clearly states the tool's verb ('filter and page') and resource ('local support ticket queue'), distinguishing it from siblings like get_ticket (which fetches a single ticket). However, it does not explicitly name a sibling for contrast, so it falls just short of a 5.

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?

The description implies usage for browsing ticket lists via filtering/pagination, but it provides no explicit when-to-use guidance or alternatives. Since no exclusions are stated, the context is clear but minimal.

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

Deploy Server