Skip to main content
Glama

get-my-member-info

Retrieve your Dooray member profile and ID to authenticate and enable task management operations like filtering by assignee.

Instructions

Get information about the authenticated user.

This tool retrieves your Dooray member profile using your API token. Most importantly, it returns your member ID which is needed for other operations like filtering tasks by assignee.

No parameters needed - it automatically uses your authentication token.

Examples:

  • Get my info: {} (empty parameters)

  • "What's my Dooray member ID?"

  • "Show my Dooray profile"

Returns your complete member profile including:

  • id: Your member ID (important for task queries)

  • name, email, organization

  • locale, timezone settings

  • display preferences

This is often the first tool to call to get your member ID for use in other tools like list-tasks.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function that executes the tool logic: calls the common API to retrieve the authenticated user's member information, returns it as formatted JSON in the MCP content format, or an error message if failed.
    export async function getMyMemberInfoHandler(args: GetMyMemberInfoInput) {
      try {
        const result = await commonApi.getMyMemberInfo();
    
        return {
          content: [
            {
              type: 'text',
              text: JSON.stringify(result, null, 2),
            },
          ],
        };
      } catch (error) {
        return {
          content: [
            {
              type: 'text',
              text: `Error: ${formatError(error)}`,
            },
          ],
          isError: true,
        };
      }
    }
  • Zod schema for input validation. This tool takes no parameters (empty object).
    export const getMyMemberInfoSchema = z.object({});
  • src/index.ts:45-45 (registration)
    Registration of the tool in the central toolRegistry, mapping the tool name to its handler and schema functions for execution and validation.
    'get-my-member-info': { handler: getMyMemberInfoHandler, schema: getMyMemberInfoSchema },
  • Core API helper function that makes the HTTP GET request to Dooray's /common/v1/members/me endpoint to fetch the current authenticated member's information.
    export async function getMyMemberInfo(): Promise<MyMemberInfo> {
      const client = getClient();
      return client.get(`${COMMON_BASE}/members/me`);
    }
  • src/index.ts:70-70 (registration)
    The tool object is added to the tools list array used for listing available tools in MCP (list_tools request).
    getMyMemberInfoTool,
Behavior4/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It effectively explains that the tool uses the API token automatically, requires no parameters, and returns the complete member profile. However, it doesn't mention potential limitations like rate limits or error conditions.

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 well-structured and front-loaded with the core purpose, followed by usage guidance, examples, and return details. Every sentence adds value without redundancy, and the bulleted list efficiently presents return fields without unnecessary elaboration.

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 0-parameter tool with no annotations and no output schema, the description provides excellent context about what the tool does, when to use it, and what it returns. The only minor gap is the lack of explicit output structure documentation, though the bulleted list partially compensates for this.

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?

The input schema has 0 parameters with 100% coverage, so the baseline would be 3. The description adds significant value by explicitly stating 'No parameters needed - it automatically uses your authentication token' and providing example usage with empty parameters, which helps the agent understand how to invoke it correctly.

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 specific action ('Get information about the authenticated user') and resource ('Dooray member profile'), distinguishing it from sibling tools like get-task or get-project-list by focusing on the user's own profile rather than project/task data. It explicitly mentions retrieving the member ID for use in other operations.

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?

The description provides explicit guidance on when to use this tool ('often the first tool to call to get your member ID for use in other tools like list-tasks') and includes practical examples of use cases. It clearly differentiates this from other tools by emphasizing its role in obtaining authentication context.

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