Skip to main content
Glama
jhl8041

Dooray MCP Server

by jhl8041
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

update-tag-group

Destructive

Update tag group settings in a Dooray project to make tag selection required or optional and limit selection to one tag or allow multiple tags.

Instructions

Update tag group settings in a Dooray project.

Tag Group Settings:

  • mandatory: When true, at least one tag from this group must be assigned when creating/updating tasks

  • selectOne: When true, exactly ONE tag from this group can be selected. When false, multiple tags can be selected

Common Configurations:

  1. Required single selection (e.g., Priority, Status): {"mandatory": true, "selectOne": true}

    • User MUST select exactly one tag

  2. Required multiple selection (e.g., Categories, Skills): {"mandatory": true, "selectOne": false}

    • User MUST select at least one tag, can select multiple

  3. Optional single selection: {"mandatory": false, "selectOne": true}

    • User can optionally select one tag

  4. Optional multiple selection (default): {"mandatory": false, "selectOne": false}

    • User can optionally select multiple tags

Finding Tag Group ID: Use get-tag-list to find tags and their tagGroup information:

{
  "tagGroup": {
    "id": "group123",  // Use this as tagGroupId
    "name": "Priority",
    "mandatory": false,
    "selectOne": false
  }
}

Examples:

  • Make group required with single selection: {"projectId": "123", "tagGroupId": "group456", "mandatory": true, "selectOne": true}

  • Allow multiple selections: {"projectId": "123", "tagGroupId": "group456", "selectOne": false}

Note: Only provide the settings you want to change. Omitted settings will not be modified.

Input Schema

NameRequiredDescriptionDefault
mandatoryNoIf true, at least one tag from this group is required when creating tasks
projectIdYesProject ID
selectOneNoIf true, exactly one tag must be selected. If false, multiple tags can be selected
tagGroupIdYesTag group ID (found in tagGroup.id from get-tag-list or get-tag response)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.2.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already flag this as a destructive, open-world mutation, so the description does not need to re-establish that. It does add real value beyond them: the downstream effect that a group's setting changes what is required when creating/updating tasks, and the important contract that omitted settings are left untouched (partial update, not full replace). It stops short of noting that flipping mandatory can affect existing tasks or that changes are not trivially reversible.

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

Conciseness3/5

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

Well organized with headers and examples, but over half the text is a combinatorial restatement of two booleans plus examples that repeat the same combinations a third time. The scenario table and the two examples are largely redundant with each other and with the parameter descriptions.

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

Completeness4/5

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

For a 4-parameter mutation with no output schema and full destructive annotations, this covers everything needed to invoke it correctly: the settings' meaning, the partial-update rule, and how to find the ID. Only the side effects on already-existing tasks are left unstated.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3; the description goes further by explaining the joint semantics of mandatory+selectOne and by telling the agent exactly where to obtain tagGroupId (tagGroup.id from get-tag-list). The repetition between the scenario list and the examples keeps it from being maximally efficient, but the added meaning is genuine.

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?

Opens with a specific verb and resource ('Update tag group settings in a Dooray project') and immediately enumerates the two mutable settings. An agent can tell this apart from create-tag and get-tag-list, the latter of which is explicitly named as the source of the required ID.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The four configuration scenarios and the worked examples make clear which combinations of mandatory/selectOne correspond to real-world setups, and the closing note states the partial-update contract. It lacks explicit 'do not use this for X, use Y instead' guidance (e.g., vs. create-tag or a tag-deletion tool), but the context is otherwise unambiguous.

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