Skip to main content
Glama
jhl8041

Dooray MCP Server

by jhl8041
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get-project-template-list

Read-onlyIdempotent

Retrieve available task templates in a Dooray project to reuse predefined titles and content for common task types. Supports pagination for browsing all templates.

Instructions

Get list of project task templates.

Templates are pre-created task structures with predefined title and body content. This tool retrieves all available templates in a project.

URL Pattern Recognition: When given a Dooray URL like "https://nhnent.dooray.com/task/PROJECT_ID", extract the PROJECT_ID (the first numeric ID after "/task/") and use it as the projectId parameter.

Note: Returns compact response with essential fields only (id and templateName).

Pagination:

  • Default page size is 20 (maximum: 100)

  • Use page parameter to get additional pages if totalCount > size

  • Set size parameter to control items per page (max: 100)

Examples:

  • Get all templates (first page): {"projectId": "123456"}

  • Get second page: {"projectId": "123456", "page": 1, "size": 20}

  • Get with custom page size: {"projectId": "123456", "page": 0, "size": 50}

Returns a paginated response with totalCount and an array of templates containing id and templateName.

Templates help users quickly create tasks with predefined structure and content, useful for common task types like bug reports, feature requests, or documentation tasks.

Input Schema

NameRequiredDescriptionDefault
pageNoPage number for pagination (default: 0)
sizeNoNumber of items per page (default: 20, max: 100)
projectIdYesProject ID to get templates from

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/openWorld, so the description focuses on adding value: it discloses the compact response shape (id and templateName only) and the pagination contract including totalCount. This is useful beyond what the annotations convey, though it doesn't mention rate limits or ordering.

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?

Front-loaded with the core purpose, then structured sections for URL recognition and pagination. The pagination rules are restated in the closing paragraph and the final sentence about template usefulness is mild filler, but overall it remains scannable.

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

Completeness5/5

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

No output schema exists, and the description fully describes the return payload (totalCount plus array of id/templateName). For a simple three-parameter read tool, an agent has everything needed to call it correctly.

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 earns an extra point by explaining how to extract projectId from a Dooray URL and by clarifying page/size behavior with worked examples beyond the schema text.

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 list of project task templates', and clarifies it retrieves all templates in a project. It does not explicitly distinguish itself from the singular sibling get-project-template, leaving the list-vs-single choice to inference.

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?

Explains what templates are and gives a clear URL-pattern recipe for deriving projectId, plus concrete pagination guidance. It stops short of naming when to use the sibling get-project-template instead, so no explicit exclusion is provided.

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