Skip to main content
Glama
umzcio
by umzcio

tdx-ticket-create

Create new tickets in TeamDynamix for IT service management, specifying type, title, priority, responsible parties, and custom attributes.

Instructions

Create a new TDX ticket

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
appIdNoTDX app ID (defaults to env TDX_APP_ID)
typeIdYesTicket type ID
titleYesTicket title
descriptionNoTicket description (HTML)
accountIdNoAccount/department ID
priorityIdNoPriority ID
statusIdNoStatus ID
requestorUidNoRequestor person UID
responsibleUidNoResponsible person UID
responsibleGroupIdNoResponsible group ID
formIdNoForm ID
sourceIdNoSource ID
serviceIdNoService ID
goesOffHoldDateNoISO date when ticket goes off hold
attributesNoCustom attributes

Implementation Reference

  • The handler for tdx-ticket-create which prepares the request body and calls the TDX client.
    async (params) => {
      const app = params.appId ?? defaultAppId;
      const body: Record<string, unknown> = {
        TypeID: params.typeId,
        Title: params.title,
      };
      if (params.description !== undefined) body.Description = params.description;
      if (params.accountId !== undefined) body.AccountID = params.accountId;
      if (params.priorityId !== undefined) body.PriorityID = params.priorityId;
      if (params.statusId !== undefined) body.StatusID = params.statusId;
      if (params.requestorUid !== undefined) body.RequestorUid = params.requestorUid;
      if (params.responsibleUid !== undefined) body.ResponsibleUid = params.responsibleUid;
      if (params.responsibleGroupId !== undefined) body.ResponsibleGroupID = params.responsibleGroupId;
      if (params.formId !== undefined) body.FormID = params.formId;
      if (params.sourceId !== undefined) body.SourceID = params.sourceId;
      if (params.serviceId !== undefined) body.ServiceID = params.serviceId;
      if (params.goesOffHoldDate !== undefined) body.GoesOffHoldDate = params.goesOffHoldDate;
      if (params.attributes) {
        body.Attributes = params.attributes.map((a) => ({ ID: a.id, Value: String(a.value) }));
      }
      try {
        const result = await client.post(`/${app}/tickets`, body);
        return { content: [{ type: "text", text: JSON.stringify(result, null, 2) }] };
      } catch (e: unknown) {
        return { content: [{ type: "text", text: String(e) }], isError: true };
      }
    }
  • The Zod schema definition for the input parameters of tdx-ticket-create.
    {
      appId: z.number().optional().describe("TDX app ID (defaults to env TDX_APP_ID)"),
      typeId: z.number().describe("Ticket type ID"),
      title: z.string().describe("Ticket title"),
      description: z.string().optional().describe("Ticket description (HTML)"),
      accountId: z.number().optional().describe("Account/department ID"),
      priorityId: z.number().optional().describe("Priority ID"),
      statusId: z.number().optional().describe("Status ID"),
      requestorUid: z.string().optional().describe("Requestor person UID"),
      responsibleUid: z.string().optional().describe("Responsible person UID"),
      responsibleGroupId: z.number().optional().describe("Responsible group ID"),
      formId: z.number().optional().describe("Form ID"),
      sourceId: z.number().optional().describe("Source ID"),
      serviceId: z.number().optional().describe("Service ID"),
      goesOffHoldDate: z.string().optional().describe("ISO date when ticket goes off hold"),
      attributes: z.array(z.object({
        id: z.number().describe("Custom attribute ID"),
        value: z.union([z.string(), z.number(), z.boolean()]).describe("Attribute value"),
      })).optional().describe("Custom attributes"),
    },
  • Registration of the tdx-ticket-create tool on the MCP server.
    server.tool(
      "tdx-ticket-create",
      "Create a new TDX ticket",
      {
        appId: z.number().optional().describe("TDX app ID (defaults to env TDX_APP_ID)"),
        typeId: z.number().describe("Ticket type ID"),
        title: z.string().describe("Ticket title"),
        description: z.string().optional().describe("Ticket description (HTML)"),
        accountId: z.number().optional().describe("Account/department ID"),
        priorityId: z.number().optional().describe("Priority ID"),
        statusId: z.number().optional().describe("Status ID"),
        requestorUid: z.string().optional().describe("Requestor person UID"),
        responsibleUid: z.string().optional().describe("Responsible person UID"),
        responsibleGroupId: z.number().optional().describe("Responsible group ID"),
        formId: z.number().optional().describe("Form ID"),
        sourceId: z.number().optional().describe("Source ID"),
        serviceId: z.number().optional().describe("Service ID"),
        goesOffHoldDate: z.string().optional().describe("ISO date when ticket goes off hold"),
        attributes: z.array(z.object({
          id: z.number().describe("Custom attribute ID"),
          value: z.union([z.string(), z.number(), z.boolean()]).describe("Attribute value"),
        })).optional().describe("Custom attributes"),
      },
      async (params) => {
        const app = params.appId ?? defaultAppId;
        const body: Record<string, unknown> = {
          TypeID: params.typeId,
          Title: params.title,
        };
        if (params.description !== undefined) body.Description = params.description;
        if (params.accountId !== undefined) body.AccountID = params.accountId;
        if (params.priorityId !== undefined) body.PriorityID = params.priorityId;
        if (params.statusId !== undefined) body.StatusID = params.statusId;
        if (params.requestorUid !== undefined) body.RequestorUid = params.requestorUid;
        if (params.responsibleUid !== undefined) body.ResponsibleUid = params.responsibleUid;
        if (params.responsibleGroupId !== undefined) body.ResponsibleGroupID = params.responsibleGroupId;
        if (params.formId !== undefined) body.FormID = params.formId;
        if (params.sourceId !== undefined) body.SourceID = params.sourceId;
        if (params.serviceId !== undefined) body.ServiceID = params.serviceId;
        if (params.goesOffHoldDate !== undefined) body.GoesOffHoldDate = params.goesOffHoldDate;
        if (params.attributes) {
          body.Attributes = params.attributes.map((a) => ({ ID: a.id, Value: String(a.value) }));
        }
        try {
          const result = await client.post(`/${app}/tickets`, body);
          return { content: [{ type: "text", text: JSON.stringify(result, null, 2) }] };
        } catch (e: unknown) {
          return { content: [{ type: "text", text: String(e) }], isError: true };
        }
      }
    );
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. 'Create a new TDX ticket' implies a write operation, but it doesn't mention required permissions, whether the creation is idempotent, what happens on failure, or any rate limits. For a mutation tool with 15 parameters and no annotation coverage, this is a significant gap in behavioral context.

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, efficient sentence with zero waste—'Create a new TDX ticket' is front-loaded and appropriately sized for its purpose. Every word earns its place without redundancy or fluff.

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 complexity (15 parameters, no output schema, no annotations), the description is inadequate. It doesn't explain what a TDX ticket is, what the tool returns, error handling, or dependencies. For a mutation tool with many parameters, more context is needed to guide effective use beyond the basic schema.

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 the schema already documents all 15 parameters thoroughly. The description adds no additional meaning about parameters beyond implying ticket creation. Baseline 3 is appropriate when the schema does the heavy lifting, though the description doesn't compensate for any gaps (there are none in this case).

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

Purpose3/5

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

The description 'Create a new TDX ticket' clearly states the action (create) and resource (TDX ticket), but it's generic and doesn't differentiate from sibling tools like 'tdx-project-create' or 'tdx-kb-create' that also create different TDX entities. It lacks specificity about what makes a ticket distinct from other TDX objects.

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?

No guidance is provided on when to use this tool versus alternatives. With siblings like 'tdx-ticket-patch' and 'tdx-ticket-update' for modifying tickets, and 'tdx-ticket-search' for finding tickets, the description offers no context on prerequisites, appropriate scenarios, or distinctions between creation and update operations.

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/umzcio/TeamDynamix-MCP-Connector'

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