Skip to main content
Glama
aliyun

AlibabaCloud DevOps MCP Server

Official
by aliyun

get_organization_member_info_by_user_id

Retrieve organization member details using user ID to access role, permissions, and profile information for Alibaba Cloud DevOps platform management.

Instructions

Get information about a member in an organization by user ID

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
organizationIdYes组织 ID
userIdYes用户 ID

Implementation Reference

  • Handler implementation for the tool: parses arguments with schema, invokes the core function getOrganizationMemberByUserIdInfoFunc, and formats response as JSON text.
    case "get_organization_member_info_by_user_id": {
      const args = types.GetOrganizationMemberByUserIdInfoSchema.parse(request.params.arguments);
      const memberInfo = await members.getOrganizationMemberByUserIdInfoFunc(args.organizationId, args.userId);
      return {
        content: [{ type: "text", text: JSON.stringify(memberInfo, null, 2)}]
      }
    }
  • Zod schema defining the input parameters for the tool: organizationId (string) and userId (string).
    export const GetOrganizationMemberByUserIdInfoSchema = z.object({
      organizationId: z.string().describe("组织 ID"),
      userId: z.string().describe("用户 ID"),
    });
  • Tool registration entry in the organization tools array, including name, description, and input schema.
    {
      name: "get_organization_member_info_by_user_id",
      description: "Get information about a member in an organization by user ID",
      inputSchema: zodToJsonSchema(types.GetOrganizationMemberByUserIdInfoSchema),
    },
  • Core helper function that performs the API request to retrieve organization member info by user ID using yunxiaoRequest to the endpoint /oapi/v1/platform/organizations/{organizationId}/members:readByUser?userId={userId}, and parses the response.
    export const getOrganizationMemberByUserIdInfoFunc = async (
      organizationId: string,
      userId: string
    ): Promise<GetOrganizationMemberInfo> => {
      const url = `/oapi/v1/platform/organizations/${organizationId}/members:readByUser`;
      const params = {
        userId: userId
      };
    
      const urlWithParams = buildUrl(url, params);
    
      const response = await yunxiaoRequest(urlWithParams, {
        method: "GET",
      });
    
      return MemberInfoSchema.parse(response);
    };
Behavior2/5

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

With no annotations provided, the description carries full burden but offers minimal behavioral insight. It states it 'gets information' but doesn't disclose whether this is a read-only operation, what permissions are required, potential rate limits, error conditions, or the format/scope of returned information. For a tool with zero annotation coverage, this is inadequate.

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 a single, efficient sentence that directly states the tool's purpose without unnecessary words. It's appropriately sized for a simple lookup tool and front-loads the core functionality.

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 no annotations and no output schema, the description is insufficient. It doesn't explain what information is returned about the member, whether authentication is required, error handling, or how it differs from similar sibling tools. The context demands more completeness for effective agent use.

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%, with both parameters clearly documented in the schema. The description adds no additional parameter semantics beyond implying the tool retrieves member information using organizationId and userId. This meets the baseline expectation when schema coverage is complete.

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 verb ('Get information') and resource ('about a member in an organization'), making the purpose specific and understandable. However, it doesn't explicitly differentiate from sibling tools like 'get_organization_member_info' or 'list_organization_members', which reduces clarity about when to choose this specific tool.

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 sibling tools like 'get_organization_member_info' (which may have different parameters) or 'list_organization_members' (which lists multiple members), leaving the agent without context for tool selection.

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/aliyun/alibabacloud-devops-mcp-server'

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