Skip to main content
Glama
jhl8041

Dooray MCP Server

by jhl8041
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get-tag

Read-onlyIdempotent

Retrieve details for a specific Dooray project tag, including its name, color, and group settings, to verify configuration before assigning it to tasks.

Instructions

Get details of a specific tag in a Dooray project.

Response Format:

{
  "id": "12345",
  "name": "Priority:High",
  "color": "ff0000",
  "tagGroup": {
    "id": "group123",
    "name": "Priority",
    "mandatory": true,
    "selectOne": true
  }
}

Response Fields:

  • id: Tag ID

  • name: Tag name (includes group prefix if it's a group tag)

  • color: Hex color code without #

  • tagGroup: Tag group information (null for individual tags)

    • id: Group ID

    • name: Group name

    • mandatory: If true, at least one tag from this group is required when creating tasks

    • selectOne: If true, exactly one tag must be selected; if false, multiple tags can be selected

Examples:

  • Get tag: {"projectId": "123", "tagId": "456"}

Use Cases:

  • Check tag details before assigning to a task

  • Verify tag group settings (mandatory, selectOne)

  • Get tag color and group information

Input Schema

NameRequiredDescriptionDefault
tagIdYesTag ID to get details for
projectIdYesProject ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.2.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent and openWorld, so the safety profile is covered; the description goes further by disclosing the exact return shape and the meaning of tagGroup.mandatory/selectOne, which an agent cannot infer elsewhere since there is no output schema. It omits what happens when the tag or project is not found.

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?

Purpose is front-loaded in the first sentence, then structured into response format, field semantics, example and use cases. The JSON sample and the field list partially duplicate each other, but each block contributes (structure vs. semantic meaning of mandatory/selectOne).

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 read-only two-parameter lookup with no output schema, the description supplies the response shape and interprets the non-obvious group flags, which is what an agent needs to act on the result. Missing only error/not-found behavior and permission prerequisites.

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?

Both parameters are already 100% described in the schema, and the description only adds a bare example ({"projectId": "123", "tagId": "456"}) without explaining ID formats or sourcing (e.g., where tagId comes from, whether the project prefix is needed). Baseline 3 applies since the schema carries the parameter burden.

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?

States a specific verb and resource ("Get details of a specific tag in a Dooray project"), which clearly separates it from the plural sibling get-tag-list. It never explicitly names get-tag-list as the alternative for listing, so distinguishability is implied by 'specific' rather than stated.

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 Use Cases block gives concrete situations (checking details before assigning to a task, verifying group settings, reading color/group info), which is real guidance beyond restating the purpose. It lacks any when-not-to-use or explicit routing to get-tag-list, so it stops short of full guidance.

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