Skip to main content
Glama
bestpractical

mcp-server-rt

Official

create_ticket

Destructive

Create a new ticket in Request Tracker by providing queue and subject, along with optional settings for content, priority, due date, custom fields, and attachments.

Instructions

Create a new ticket in RT

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
CcNoCc username(s) (string or array of strings)
DueNoDue datetime (format: "YYYY-MM-DD HH:MM:SS" in local time)
ToldNoLast Contact datetime (format: "YYYY-MM-DD HH:MM:SS" in local time)
TypeNoTicket type (e.g. "ticket", "reminder")
ChildNoChild links (ticket ID, URL, or array)
OwnerNoOwner username
QueueYesQueue name or ID
ParentNoParent links (ticket ID, URL, or array)
StartsNoStarts datetime (format: "YYYY-MM-DD HH:MM:SS" in local time)
StatusNoInitial status
AdminCcNoAdminCc username(s) (string or array of strings)
ContentNoTicket body content
StartedNoStarted datetime (format: "YYYY-MM-DD HH:MM:SS" in local time)
SubjectYesTicket subject
PriorityNoTicket priority
RefersToNoRefersTo links (ticket ID, URL, or array)
DependsOnNoDependsOn links (ticket ID, URL, or array)
RequestorNoRequestor username(s) (string or array of strings)
AttachmentsNoFiles to attach. Provide either FilePath (local file path, server reads and encodes it) or FileContent (pre-encoded MIME Base64). FileName and FileType are optional with FilePath and are inferred from the path.
ContentTypeNoContent MIME type (default text/plain)
CustomRolesNoCustom role assignments as {role_name: username_or_array}
DescriptionNoTicket description
CustomFieldsNoCustom field values as {CF_name: value}
DependedOnByNoDependedOnBy links (ticket ID, URL, or array)
ReferredToByNoReferredToBy links (ticket ID, URL, or array)
Behavior2/5

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

Annotations declare destructiveHint=true, and the description does not contradict. However, the description adds no behavioral context beyond the action itself—no mention of side effects, permissions, or that a new ticket is created. It merely restates the purpose without disclosing additional behavior.

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, front-loaded sentence with no wasted words. It is perfectly concise for the simple action it states.

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?

Despite high schema coverage, the tool is complex with 25 parameters, nested objects, and no output schema. The description does not explain return values (e.g., ticket ID) or provide an operational overview, leaving the agent to rely entirely on the schema. This is insufficient for such a complex tool.

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 descriptions cover 100% of 25 parameters, including detailed explanations for nested objects like Attachments and CustomFields. The description adds no parameter-level information, so baseline 3 applies.

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?

Description uses a specific verb 'Create' and resource 'ticket' in 'RT', clearly distinguishing it from sibling tools like update_ticket, add_comment, and search_tickets. The scope 'in RT' adds context and leaves no ambiguity about the tool's purpose.

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

Usage Guidelines3/5

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

No explicit guidance on when to use this tool vs alternatives. It is implied by the name and description that this creates new tickets, but there is no mention of when not to use it (e.g., for modifications use update_ticket) or prerequisites beyond required fields.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/bestpractical/mcp-server-rt'

If you have feedback or need assistance with the MCP directory API, please join our Discord server