Skip to main content
Glama

Get support ticket

get_support_ticket
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. Show one support ticket in full: subject, description, status, severity, the related cluster, who reported it, the conversation with Ankra support (customer replies and support answers) and the attachments' names. Identify it by ticket_number (the number people quote) or ticket_id. Read-only. To answer a question support asked, use comment_support_ticket.

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

Input Schema

NameRequiredDescriptionDefault
ticket_idNoThe support ticket UUID. Optional when ticket_number is given.
ticket_numberNoThe per-organisation support ticket number.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

The readOnlyHint annotation already covers safety, but the description adds real value by enumerating the returned payload (status, severity, cluster, reporter, full conversation thread, attachment names), which matters because there is no output schema. The 'Read-only' restatement duplicates the annotation rather than adding to it, and nothing is said about what happens when both ticket_id and ticket_number are supplied or when neither is.

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 the critical scoping constraint ("Legacy Platform support desk only") before any detail, and the sibling routing follows immediately. The middle sentence is a long comma-list of return fields that is slightly dense but every element is substantive; nothing is padding.

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?

For a two-optional-parameter read tool with no output schema, the description carries the return-value burden well by listing the fields returned. The one meaningful gap is the edge case that both parameters are optional with zero required, so the description could state that one identifier must be supplied.

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 already 100%, yet the description still adds meaning: ticket_number is glossed as 'the number people quote' (human-facing vs. the UUID), and the two identifiers are framed as alternatives for locating the same ticket. It stops short of saying which wins if both are passed or that at least one is needed.

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?

"Show one support ticket in full" gives a specific verb and resource, and the sentence then enumerates exactly what 'in full' means (subject, description, status, severity, cluster, reporter, conversation, attachment names). The opening line scoping it to the Legacy Platform support desk cleanly separates it from support_get_ticket and the support.* family.

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?

Explicit when-to-use and when-not-to-use: legacy desk only, and new requests / support.ankra.app conversations should go to support_create_ticket, support_list_tickets, support_get_ticket and support_reply. It also routes the follow-up action ("To answer a question support asked, use comment_support_ticket"), so the agent has no inference left to do.

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.