Skip to main content
Glama
Teamwork

Teamwork

Official
by Teamwork
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Go
Remote

twdesk-update_status

Update a ticket status by ID, adjusting its name, color, or display order as needed. Keep status labels aligned with your team's workflow.

Instructions

Update ticket status.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesThe ID of the status to update.
nameNoThe new name of the status.
colorNoThe color of the status.
displayOrderNoThe display order of the status.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changedv1.39.3
    • removedInput schema / properties / color / anyOf
      Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
    • addedInput schema / properties / color / type
      Added value: +"string"
    • removedInput schema / properties / displayOrder / anyOf
      Removed value: -[
-  {
-    "type": "integer"
-  },
-  {
-    "type": "null"
-  }
-]
    • addedInput schema / properties / displayOrder / type
      Added value: +"integer"
    • removedInput schema / properties / name / anyOf
      Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
    • addedInput schema / properties / name / type
      Added value: +"string"
    • changedInput schema / required
      Previous value: -[
-  "id",
-  "name",
-  "color",
-  "displayOrder"
-]New value: +[
+  "id"
+]
  2. Addedv1.26.0
  3. Removedv1.25.0
  4. Changed2 schema fields changedv1.20.1
    • addedInput schema / additionalProperties
      Added value: +false
    • changedInput schema / required
      Previous value: -[
-  "id"
-]New value: +[
+  "id",
+  "name",
+  "color",
+  "displayOrder"
+]
  5. Addedv1.18.3
  6. Removedv1.18.2
  7. Addedv1.17.2

TDQS

C2.4/5.0
Behavior2/5

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

Annotations already indicate this is a mutating action (readOnlyHint=false) and not destructive (destructiveHint=false). The description adds no behavioral detail beyond the generic word 'update' — it does not mention partial-update semantics, whether only provided fields are changed, validation behavior, or what happens to tickets already using the status.

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

Conciseness2/5

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

The description is extremely short, but it is under-specified rather than appropriately concise. 'Update ticket status' largely restates the tool's purpose and omits the field-level and contextual detail needed to avoid ambiguity.

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 an update tool, the description lacks clarity about what entity is updated and what effects the operation has. The schema covers parameters, but the description does not tie together the status definition concept, optional fields, or distinguish this from updating a ticket's status field. Given no output schema and no usage guidance, the description is only minimally adequate.

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?

The input schema provides descriptions for all four parameters (id, name, color, displayOrder), giving 100% schema description coverage. The description adds no parameter-level meaning, but the coverage baseline applies, so this is adequate.

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 states a clear verb ('update') and a resource ('ticket status'), so it is not a tautology. However, 'ticket status' is ambiguous: it could mean updating a field on a ticket or updating a status definition entity. Given the schema exposes name, color, and displayOrder, it likely means the latter, but the description does not disambiguate this, nor does it distinguish itself from twdesk-update_ticket.

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?

There is no guidance on when to use this tool versus alternatives such as twdesk-create_status, twdesk-get_status, or twdesk-update_ticket. The description provides no context about prerequisites, exclusions, or scenarios where another tool would be more appropriate.

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