Skip to main content
Glama
Sign In
Support Ticket Triage MCP

Support Ticket Triage MCP

by MatiasLaukka
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

reject_triage_recommendation

Destructive

Record feedback to reject a triage recommendation and finalize the proposal.

Instructions

Finalize a local triage proposal as rejected and record feedback.

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": {
      "recommendationId": "<recommendationId>",
      "ticketId": "<ticketId>",
      "actor": "<actor>",
      "feedback": "<feedback>"
    },
    "name": "reject_triage_recommendation"
  }
}

Input Schema

NameRequiredDescriptionDefault
actorYes
feedbackYes
ticketIdYes
recommendationIdYes

Output Schema

NameRequiredDescriptionDefault
auditEventYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already indicate destructiveHint=true, so the safety profile is known. The description adds minimal context by mentioning 'record feedback', but it does not explain consequences like irreversibility or state changes beyond what annotations imply.

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

Conciseness5/5

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

The description is a single, clear sentence that is front-loaded with the action and outcome. No wasted words.

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?

Given the destructive nature and 4 required parameters, the description is too sparse. It does not explain side effects, prerequisites, or how rejection fits into the workflow, even though an output schema exists.

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?

With 0% schema description coverage, the description must compensate, but it only implicitly references 'feedback'. It does not clarify the meaning or relationships of recommendationId, ticketId, or actor, leaving the agent to infer from parameter names alone.

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?

The description uses a specific verb ('Finalize') and identifies the resource ('local triage proposal') and the outcome ('as rejected and record feedback'). It clearly distinguishes this from sibling tools like approve_triage_recommendation and submit_triage_recommendation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives (e.g., approve_triage_recommendation). It simply states what the tool does without context about the decision process or prerequisites.

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

Deploy Server

Other Tools