Skip to main content
Glama
Teamwork

Teamwork

Official
by Teamwork
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Go
Remote

twdesk-update_tag

Update a Desk tag's name and color using its ID to keep support tags accurate and organized.

Instructions

Update Desk tag.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesThe ID of the tag to update.
nameNoThe new name of the tag.
colorNoThe color of the tag.

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 / name / anyOf
      Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
    • addedInput schema / properties / name / type
      Added value: +"string"
    • changedInput schema / required
      Previous value: -[
-  "id",
-  "name",
-  "color"
-]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"
+]
  5. Addedv1.18.3
  6. Removedv1.18.2
  7. Addedv1.17.2

TDQS

B3.2/5.0
Behavior2/5

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

The description only restates that the tool mutates a Desk tag, which annotations already convey via readOnlyHint=false. It adds no context about side effects, permission requirements, partial-update semantics, or behavior when optional fields are omitted. It does not contradict the annotations, but it adds no behavioral value beyond them.

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 short sentence with no filler, and the verb 'Update' is front-loaded. It is appropriately concise for a simple tool, though it provides no structural elaboration such as usage hints or caveats.

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 update tool with complete schema coverage and annotations, the description provides just enough to identify the target resource. However, it does not address when to choose this over sibling tag-update tools, nor does it describe update behavior beyond the schema. It is minimally viable but not fully complete.

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%, and each parameter (id, name, color) already has a meaningful description. The tool description adds no parameter-level detail, but none is strictly needed because the schema fully documents the parameters. A baseline score of 3 is appropriate.

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?

The description states a specific verb and resource: 'Update Desk tag.' The 'Desk' qualifier distinguishes this from sibling tools like twprojects-update_tag and twspaces-update_tag. An agent can immediately understand what the tool operates on.

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?

The description gives no explicit guidance on when to use this tool versus alternatives such as twprojects-update_tag or twspaces-update_tag. It does not state prerequisites, exclusions, or context in which this update operation should be preferred. The only signal is the 'Desk' qualifier, which is implied rather than explained.

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