Skip to main content
Glama

Close support ticket

close_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. Close a support ticket from the customer's side, the same action as ankra support close: the ticket is marked closed and a 'closed by the customer' note is added to the thread. Use it only when the user says the matter is resolved or no longer needed; do not close on support's behalf. Identify the ticket by ticket_number or ticket_id. Note the support team's own board is not moved by this close (a known gap): if support is still expected to act, reply with comment_support_ticket instead.

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": "close_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.6/5.0
Behavior5/5

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

Annotations already declare destructiveHint=true and non-idempotent, but the description adds material context they don't carry: the exact side effects (status change plus thread note), which side of the ticket is acting, and a documented known gap that the support team's board is not moved. It also flags the legacy-platform restriction, so an agent won't misuse it on the newer support.ankra.app surface.

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?

Dense but well ordered: platform scope, sibling routing, action semantics, usage condition, identification, then the known-gap caveat with its alternative. Slightly long due to enumerating four sibling tool names, but nearly every clause carries actionable information.

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?

For a two-parameter destructive mutation with no output schema, the description covers scope, preconditions, side effects, the customer-vs-support distinction, identification, and the limitation around the support board. An agent has enough to call it correctly or avoid it.

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 both parameters are already documented as ticket UUID and per-organisation number. The description only restates that identification can be by either field, without adding precedence rules or behavior when both are supplied, so it does not exceed the baseline.

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 ('Close a support ticket') and immediately scopes it to the customer's side, equating it to `ankra support close` and describing the resulting state change (marked closed plus a 'closed by the customer' note). It explicitly separates itself from the create/list/get/reply siblings by name.

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 an explicit positive condition ('only when the user says the matter is resolved or no longer needed'), an explicit prohibition ('do not close on support's behalf'), and a named alternative with its triggering condition ('if support is still expected to act, reply with comment_support_ticket instead'). Routing decisions are fully determined.

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.