Skip to main content
Glama
umzcio
by umzcio

tdx-ticket-patch

Update specific fields in a TDX ticket without modifying the entire record. Use this tool to modify partial ticket data in TeamDynamix for targeted IT service management changes.

Instructions

Partial update of a TDX ticket (only specified fields)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
appIdNoTDX app ID (defaults to env TDX_APP_ID)
idYesTicket ID
dataYesPartial ticket data (PascalCase TDX field names)

Implementation Reference

  • The `tdx-ticket-patch` tool is registered and implemented within `src/tools/tickets.ts`. It takes a ticket ID and a data record, performing a PATCH request using the `TdxClient`.
    server.tool(
      "tdx-ticket-patch",
      "Partial update of a TDX ticket (only specified fields)",
      {
        appId: z.number().optional().describe("TDX app ID (defaults to env TDX_APP_ID)"),
        id: z.number().describe("Ticket ID"),
        data: z.record(z.unknown()).describe("Partial ticket data (PascalCase TDX field names)"),
      },
      async (params) => {
        const app = params.appId ?? defaultAppId;
        try {
          const result = await client.patch(`/${app}/tickets/${params.id}`, params.data);
          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 full burden. It states it's a partial update, implying mutation, but doesn't disclose behavioral traits like required permissions, whether changes are reversible, rate limits, or what happens to unspecified fields. This is inadequate for a mutation tool with zero annotation coverage.

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. It's front-loaded with the core purpose and appropriately sized for the tool's complexity.

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?

For a mutation tool with no annotations and no output schema, the description is incomplete. It lacks details on behavioral context, error handling, and output expectations, leaving significant gaps for an agent to use it correctly.

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 documents all parameters. The description adds minimal value beyond the schema by implying 'data' contains partial fields, but doesn't explain syntax or format details like PascalCase usage beyond what's in the schema descriptions.

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?

The description clearly states the action ('partial update') and resource ('TDX ticket'), specifying it only modifies specified fields. It distinguishes from sibling 'tdx-ticket-update' by implying that tool might be a full update, though not explicitly stated.

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 explicit guidance on when to use this tool versus alternatives like 'tdx-ticket-update' or 'tdx-ticket-create'. The description implies usage for partial updates but lacks context on prerequisites, error conditions, or comparisons to siblings.

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