Skip to main content
Glama

Create support ticket

create_support_ticket
Destructive

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. Raise a support ticket with Ankra's support team on the user's behalf - the same request ankra support create files. Use it when the user asks to contact support, report a platform problem to Ankra, or escalate something the platform cannot fix itself; do not use it for work the AI board should track (file_ticket). Write a specific subject and a description with the evidence: what was expected, what happened, when, and which cluster or resource. The ticket reaches the support team and the user receives a confirmation email. Defaults to the session's cluster when none is given.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "subject": "<subject>",
      "description": "<description>"
    },
    "name": "create_support_ticket"
  }
}

Input Schema

NameRequiredDescriptionDefault
subjectYesShort summary of the issue (at most 200 characters).
categoryNoThe kind of request (default 'technical').
severityNoHow urgent it is for the user. Omit to let support triage it.
cluster_idNoThe cluster the request concerns (UUID). Defaults to the session's cluster when scoped.
descriptionYesWhat was expected, what happened, when, and the evidence (markdown, at most 10000 characters).

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?

Adds real behavior beyond the annotations: the ticket reaches the support team, the user receives a confirmation email, and the scope defaults to the session's cluster. It does not flag that the call is non-idempotent (duplicate submissions create separate tickets) or what identifier comes back, which is the main remaining gap for a write tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loads the platform scoping and routing correctly, but the middle sentence is dense and slightly confusing: it bundles support_create_ticket with support_list_tickets, support_get_ticket and support_reply as if all four were drop-in alternatives for this operation. The content is useful but could be split for scanability.

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 no output schema, the description covers the outcome (ticket filed, confirmation email sent) and the scoping behavior, which is most of what an agent needs. What is missing is the returned handle (ticket ID or link) and duplicate-submission behavior, which matter for a non-idempotent write.

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 the baseline is 3, but the description adds content guidance the schema lacks: write a specific subject and describe expected vs. actual behavior, timing, and affected cluster or resource. It also restates the cluster default, which the schema already covers.

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 ('Raise a support ticket with Ankra's support team on the user's behalf') and pins it to the Legacy Platform support desk, explicitly excluding support_create_ticket for new requests and file_ticket for AI-board work. An agent can select this 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 Guidelines5/5

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

Gives explicit triggers ('when the user asks to contact support, report a platform problem to Ankra, or escalate something the platform cannot fix itself') and an explicit exclusion with a named alternative ('do not use it for work the AI board should track (file_ticket)').

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.