Skip to main content
Glama
tallpizza

Dooray MCP Server

by tallpizza

dooray_members

Search Dooray members by email or ID, retrieve detailed profiles, and check project membership status for team management.

Instructions

Manage Dooray members - search by email/ID, get member details, check project membership

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actionYesAction to perform on members
emailNoEmail address (for search_by_email)
userIdNoUser ID (for search_by_id/get_details)
projectIdNoProject ID (optional - uses default from environment if not provided)

Implementation Reference

  • The MembersTool class implements the core handler logic for the 'dooray_members' tool. The 'handle' method dispatches based on the 'action' parameter to specific member management functions using the DoorayClient.
    class MembersTool:
        """Tool for managing Dooray members."""
        
        def __init__(self, dooray_client):
            """Initialize with Dooray client."""
            self.client = dooray_client
        
        async def handle(self, arguments: Dict[str, Any]) -> str:
            """Handle members tool requests.
            
            Args:
                arguments: Tool arguments containing action and parameters
                
            Returns:
                JSON string with results
            """
            action = arguments.get("action")
            if not action:
                return json.dumps({"error": "Action parameter is required"})
            
            try:
                if action == "search_by_email":
                    return await self._search_by_email(arguments)
                elif action == "search_by_id":
                    return await self._search_by_id(arguments)
                elif action == "get_details":
                    return await self._get_details(arguments)
                elif action == "list_project_members":
                    return await self._list_project_members(arguments)
                else:
                    return json.dumps({"error": f"Unknown action: {action}"})
                    
            except Exception as e:
                logger.error(f"Error in members tool: {e}")
                return json.dumps({"error": str(e)})
        
        async def _search_by_email(self, arguments: Dict[str, Any]) -> str:
            """Search member by email address."""
            email = arguments.get("email")
            if not email:
                return json.dumps({"error": "email is required for search_by_email action"})
            
            result = await self.client.search_member_by_email(email)
            return json.dumps(result, ensure_ascii=False)
        
        async def _search_by_id(self, arguments: Dict[str, Any]) -> str:
            """Search member by user ID."""
            user_id = arguments.get("userId")
            if not user_id:
                return json.dumps({"error": "userId is required for search_by_id action"})
            
            result = await self.client.search_member_by_id(user_id)
            return json.dumps(result, ensure_ascii=False)
        
        async def _get_details(self, arguments: Dict[str, Any]) -> str:
            """Get member details."""
            user_id = arguments.get("userId")
            if not user_id:
                return json.dumps({"error": "userId is required for get_details action"})
            
            result = await self.client.get_member_details(user_id)
            return json.dumps(result, ensure_ascii=False)
        
        async def _list_project_members(self, arguments: Dict[str, Any]) -> str:
            """List members of a project."""
            project_id = arguments.get("projectId")
            
            result = await self.client.list_project_members(project_id)
            return json.dumps(result, ensure_ascii=False)
  • Input schema for the 'dooray_members' tool, defining available actions and parameters, registered in the list_tools handler.
    types.Tool(
        name="dooray_members",
        description="Manage Dooray members - search by email/ID, get member details, check project membership",
        inputSchema={
            "type": "object",
            "properties": {
                "action": {
                    "type": "string",
                    "enum": ["search_by_email", "search_by_id", "get_details", "list_project_members"],
                    "description": "Action to perform on members"
                },
                "email": {
                    "type": "string",
                    "description": "Email address (for search_by_email)"
                },
                "userId": {
                    "type": "string",
                    "description": "User ID (for search_by_id/get_details)"
                },
                "projectId": {
                    "type": "string",
                    "description": "Project ID (optional - uses default from environment if not provided)"
                }
            },
            "required": ["action"]
        }
    ),
  • Registration and dispatch point in the main tool handler (@app.call_tool()), where MembersTool is instantiated and invoked for 'dooray_members' calls.
    elif name == "dooray_members":
        tool = MembersTool(dooray_client)
        result = await tool.handle(args)
  • Import statement for the MembersTool handler class.
    from .tools.members import MembersTool
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It lists actions but doesn't explain permissions needed, rate limits, whether operations are read-only or mutating, or what happens with errors. This is inadequate for a tool with multiple action types.

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

Conciseness5/5

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

The description is extremely concise with a single sentence that efficiently lists the key capabilities. Every word earns its place with no wasted text, making it easy to parse quickly.

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

Completeness2/5

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

For a tool with 4 parameters, multiple action types, no annotations, and no output schema, the description is insufficient. It doesn't explain return values, error conditions, or behavioral nuances needed for proper tool selection and invocation.

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 documents all parameters thoroughly. The description mentions the action types but doesn't add meaningful context beyond what the schema provides about parameter usage or constraints.

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?

The description clearly states the tool's purpose as managing Dooray members with specific actions (search by email/ID, get details, check project membership). It uses specific verbs and resources, but doesn't differentiate from sibling tools like dooray_search or dooray_tasks that might also involve member operations.

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 provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites, when not to use it, or how it relates to sibling tools like dooray_search that might overlap in functionality.

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/tallpizza/dooray-mcp'

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