Skip to main content
Glama

get-project-list

Retrieve a paginated list of active projects you belong to in Dooray, excluding archived projects, for browsing when no specific project is identified.

Instructions

Get list of active projects that you belong to.

This tool retrieves only active projects where you are a member. Archived projects are excluded.

Note: Returns compact response with essential fields only. For complete project details, use get-project.

IMPORTANT: When the user provides a specific Dooray URL (e.g., "https://nhnent.dooray.com/task/PROJECT_ID"), do NOT use this tool. Instead, extract the PROJECT_ID from the URL and call get-project directly to get information about that specific project.

This tool is for browsing your active projects when no specific project URL or ID is provided.

Examples:

  • Get all your active projects: {} (empty parameters)

  • Get second page with 50 items: {"page": 1, "size": 50}

Returns a paginated list with project id and name (project code) for each project.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoPage number for pagination (default: 0)
sizeNoNumber of items per page (default: 20, max: 100)

Implementation Reference

  • The main handler function getProjectListHandler that fetches the project list from the API, filters it, and returns a formatted JSON response or error.
    export async function getProjectListHandler(args: GetProjectListInput) {
      try {
        const result = await projectsApi.getProjects({
          page: args.page,
          size: args.size,
        });
    
        // Filter to compact response to reduce token usage
        const compactResult = filterPaginatedResponse(result, filterProjectForList);
    
        return {
          content: [
            {
              type: 'text',
              text: JSON.stringify(compactResult, null, 2),
            },
          ],
        };
      } catch (error) {
        return {
          content: [
            {
              type: 'text',
              text: `Error: ${formatError(error)}`,
            },
          ],
          isError: true,
        };
      }
    }
  • Zod schema getProjectListSchema used for input validation in the server.
    export const getProjectListSchema = z.object({
      page: z.number().min(0).optional().describe('Page number for pagination (default: 0)'),
      size: z.number().min(1).max(100).optional().describe('Number of items per page (default: 20, max: 100)'),
    });
  • src/index.ts:48-48 (registration)
    Registration of the tool in the toolRegistry map used by the MCP server for handling tool calls.
    'get-project-list': { handler: getProjectListHandler, schema: getProjectListSchema },
  • src/index.ts:20-20 (registration)
    Import statement bringing in the tool components.
    import { getProjectListTool, getProjectListHandler, getProjectListSchema } from './tools/projects/get-project-list.js';
  • Tool metadata object getProjectListTool with name, description, and JSON inputSchema for tool discovery in list_tools.
    export const getProjectListTool = {
      name: 'get-project-list',
      description: `Get list of active projects that you belong to.
    
    This tool retrieves only active projects where you are a member. Archived projects are excluded.
    
    **Note**: Returns compact response with essential fields only. For complete project details, use get-project.
    
    **IMPORTANT**: When the user provides a specific Dooray URL (e.g., "https://nhnent.dooray.com/task/PROJECT_ID"), do NOT use this tool. Instead, extract the PROJECT_ID from the URL and call get-project directly to get information about that specific project.
    
    This tool is for browsing your active projects when no specific project URL or ID is provided.
    
    Examples:
    - Get all your active projects: {} (empty parameters)
    - Get second page with 50 items: {"page": 1, "size": 50}
    
    Returns a paginated list with project id and name (project code) for each project.`,
      inputSchema: {
        type: 'object',
        properties: {
          page: {
            type: 'number',
            description: 'Page number for pagination (default: 0)',
            minimum: 0,
          },
          size: {
            type: 'number',
            description: 'Number of items per page (default: 20, max: 100)',
            minimum: 1,
            maximum: 100,
          },
        },
      },
    };
Behavior4/5

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

With no annotations provided, the description carries full burden and does well: it discloses that it returns only active projects (filtering behavior), excludes archived projects, returns compact response with essential fields, is paginated, and has default values. It doesn't mention rate limits or auth needs, but covers key behavioral traits adequately for a read operation.

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?

Well-structured with clear sections (purpose, note, important warning, usage context, examples, return format). Some redundancy exists (e.g., 'Get list' and 'retrieves' in first two sentences), but overall it's appropriately sized and front-loaded with critical information.

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?

For a read-only list tool with 2 fully documented parameters and no output schema, the description is complete: it explains what the tool does, when to use it, behavioral constraints (active-only, compact response), pagination, and distinguishes from alternatives. No significant gaps given the tool's complexity.

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 schema already fully documents both parameters. The description adds minimal value beyond the schema by providing usage examples with parameters, but doesn't explain semantics or constraints beyond what's in the schema. Baseline 3 is appropriate when schema does the heavy lifting.

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 clearly states the verb ('Get list', 'retrieves') and resource ('active projects that you belong to'), specifying the scope (active projects where user is a member, excluding archived). It distinguishes from sibling 'get-project' by noting this is for listing vs. getting details.

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

Usage Guidelines5/5

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

Explicitly states when to use ('for browsing your active projects when no specific project URL or ID is provided') and when not to use (when user provides a specific Dooray URL, use 'get-project' instead). It names the alternative tool and provides clear context for usage decisions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/jhl8041/dooray-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server