Skip to main content
Glama

Create an IT ticket

ticket_create

Open a new IT helpdesk ticket with a preview by default; confirm the change after user approval to submit it. Specify title, description, category, priority, and requester.

Instructions

Open a new IT helpdesk ticket. Dry run by default: without confirm=true it only returns a preview. Get the user’s approval, then call again with confirm=true. Requires role: agent.

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": {
      "title": "<title>",
      "description": "<description>"
    },
    "name": "ticket_create"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleYes
confirmNofalse (default) = dry run that only previews the change. true = actually apply it. Ask the user before sending true.
categoryNoother
priorityNoP3
assignee_idNoEmployee id, e.g. E004
descriptionYes
requester_idNoWho the ticket is for. Defaults to the caller’s own employee id.

Output Schema

NameRequiredDescriptionDefault
ticketYes
dry_runYes
next_stepNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false and destructiveHint=false, but they cannot convey the non-obvious dry-run default, the approval gate, or the agent-role requirement — all of which the description supplies explicitly. What is missing is any warning that the call is non-idempotent (retries may create duplicate tickets) and what the preview actually contains.

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?

Four short sentences, front-loaded with the purpose and immediately followed by the highest-risk behavioral fact (dry run by default). No redundant or filler wording.

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 an output schema present, the description need not explain return values, and it covers the key operational concerns: dry run, approval step, and role requirement. Remaining gaps are duplicate-creation risk on retry and how the preview should be presented to the user.

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?

Schema description coverage is only 43%, so the description must carry the load, and it adds meaning almost exclusively for confirm — which the schema already documents in detail. The undocumented parameters (title, description, category, priority) receive no explanation of format, defaults, or impact, and assignee_id/requester_id are never mentioned.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Open a new IT helpdesk ticket" states a specific verb (open/create) and resource, which clearly separates it from ticket_get, ticket_update, and tickets_list by implication. It does not explicitly name a sibling as the alternative path, so it stops short of the top mark.

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

Usage Guidelines4/5

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

The definition gives a concrete invocation workflow (dry run by default, obtain user approval, re-call with confirm=true) and a prerequisite (requires role: agent). It does not state when to prefer ticket_update or tickets_list instead, but the create-vs-modify distinction is largely implied by "Open a new".

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