Skip to main content
Glama
Teamwork

Teamwork

Official
by Teamwork
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Go
Remote

twdesk-create_status

Add a new ticket status to Teamwork Desk with name, color, and display order. Define custom states to fit your support workflow.

Instructions

Create ticket status.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesThe name of the status.
colorNoThe color of the status.
displayOrderNoThe display order of the status.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 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"
    • changedInput schema / required
      Previous value: -[
-  "name",
-  "color",
-  "displayOrder"
-]New value: +[
+  "name"
+]
  2. Changed2 schema fields changedv1.20.1
    • addedInput schema / additionalProperties
      Added value: +false
    • changedInput schema / required
      Previous value: -[
-  "name"
-]New value: +[
+  "name",
+  "color",
+  "displayOrder"
+]
  3. Addedv1.18.3
  4. Removedv1.18.2
  5. Addedv1.17.2

TDQS

C2.9/5.0
Behavior2/5

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

The description adds little beyond the annotations: it repeats the creation action and adds the 'ticket' domain qualifier. It does not disclose whether duplicate names are rejected, whether color or displayOrder have defaults, or what the API returns after creation.

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

Conciseness4/5

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

The description is a single economical sentence with no filler and the key action/resource are front-loaded. It is under-specified in behavioral terms, but this is a conciseness issue rather than verbosity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple create operation with fully documented parameters, this is minimally adequate. However, with no output schema, the description does not clarify return behavior, side effects, or uniqueness constraints, leaving moderate gaps for an agent selecting or invoking the 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 description coverage is 100%, so the input schema already documents name, color, and displayOrder completely. The description adds no parameter-level meaning, but the schema fully carries that burden, so the baseline score of 3 is appropriate.

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 states a clear verb ('create') and resource ('ticket status'), which is specific enough to distinguish from sibling tools like twdesk-create_priority or twdesk-create_ticket_type. It does not explicitly contrast with update_status or list_statuses, but the core purpose is unambiguous.

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 such as twdesk-update_status for modifying statuses or twdesk-list_statuses for viewing existing ones. An agent must infer usage entirely from the tool name and sibling list.

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