Skip to main content
Glama

List support tickets

list_support_tickets
Read-only

Legacy Platform support desk only. For new requests and support.ankra.app conversations use support_create_ticket, support_list_tickets, support_get_ticket and support_reply. List the organisation's support tickets with Ankra support (the requests ankra support and the portal's Support page show), newest first, with status, category, severity and the related cluster. Filter by status, cluster or a search over subject and description. Read-only. These are customer support requests to Ankra's team, not the AI work board's tickets (ticket_list).

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

Input Schema

NameRequiredDescriptionDefault
pageNoPage number (default 1).
queryNoSearch text matched against subject and description.
statusNoOnly tickets in these statuses. Omit for every status.
page_sizeNoTickets per page (default 50, at most 100).
cluster_idNoOnly tickets about this cluster (UUID).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, and the description reinforces it while adding context the annotation cannot: result ordering (newest first), the returned fields (status, category, severity, related cluster), and the fact that these are requests to Ankra's team rather than internal work items. It does not cover pagination behavior or what happens when filters match nothing.

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?

The scope boundary is correctly front-loaded and each sentence carries routing or behavioral information. The enumeration of four sibling tools in one sentence is slightly bulky, but nothing is genuinely redundant beyond the read-only reassurance.

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

Completeness5/5

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

With no output schema, the description compensates by naming the returned fields and sort order, and it resolves the highest-risk ambiguity (confusion with ticket_list and support_list_tickets) for a zero-required-param list tool. Nothing an agent needs before calling is missing.

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 100%, so the schema already documents page, page_size, query, status enum values and cluster_id as a UUID. The description only restates the filter dimensions (status, cluster, subject/description search) without adding format or interaction semantics, so baseline 3 applies.

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 (list the organisation's support tickets with Ankra support) and explicitly distinguishes itself from two lookalikes: support_list_tickets (support.ankra.app conversations) and ticket_list (AI work board tickets). An agent can select it without opening any schema.

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?

Names the platform boundary up front ('Legacy Platform support desk only'), routes new requests to the support_* family by name, and closes with an explicit exclusion against ticket_list. When-to-use and when-not-to-use are both present, with alternatives named.

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.