Skip to main content
Glama
aliyun

AlibabaCloud DevOps MCP Server

Official
by aliyun

get_organization_member_info

Retrieve member details from Alibaba Cloud DevOps organizations to manage team access and permissions using organization and member IDs.

Instructions

Get information about a member in an organization

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
organizationIdYes组织 ID
memberIdYes成员 ID

Implementation Reference

  • Handles the 'get_organization_member_info' tool request by parsing input arguments with GetOrganizationMemberInfoSchema, calling the getOrganizationMemberInfoFunc helper, and returning the member information as a JSON-formatted text response.
    case "get_organization_member_info": {
      const args = types.GetOrganizationMemberInfoSchema.parse(request.params.arguments);
      const memberInfo = await members.getOrganizationMemberInfoFunc(
        args.organizationId,
        args.memberId
      );
      return {
        content: [{ type: "text", text: JSON.stringify(memberInfo, null, 2)}]
      }
    }
  • Defines the input schema GetOrganizationMemberInfoSchema (organizationId and memberId) and the output type GetOrganizationMemberInfo inferred from MemberInfoSchema.
    export const GetOrganizationMemberInfoSchema = z.object({
      organizationId: z.string().describe("组织 ID"),
      memberId: z.string().describe("成员 ID"),
    });
    
    export type GetOrganizationMemberInfo = z.infer<typeof MemberInfoSchema>;
  • Registers the 'get_organization_member_info' tool in the tool registry, specifying name, description, and input schema derived from Zod schema.
    {
      name: "get_organization_member_info",
      description: "Get information about a member in an organization",
      inputSchema: zodToJsonSchema(types.GetOrganizationMemberInfoSchema),
    },
  • Core helper function getOrganizationMemberInfoFunc that performs the API GET request to retrieve organization member details and validates the response using MemberInfoSchema.
    export const getOrganizationMemberInfoFunc = async (
      organizationId: string,
      memberId: string
    ): Promise<GetOrganizationMemberInfo> => {
      const url = `/oapi/v1/platform/organizations/${organizationId}/members/${memberId}`;
    
      console.log("aaa", url)
      const response = await yunxiaoRequest(url, {
        method: "GET",
      });
    
      return MemberInfoSchema.parse(response);
    };
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the tool 'Get information,' implying a read-only operation, but doesn't clarify aspects like authentication requirements, rate limits, error handling, or what happens if IDs are invalid. For a tool with zero annotation coverage, this leaves significant gaps in understanding how it behaves in practice, making it inadequate for safe and effective use.

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, clear sentence: 'Get information about a member in an organization.' It's front-loaded with the core action and resource, with zero wasted words or redundancy. This makes it highly efficient and easy to parse, though its brevity contributes to gaps in other dimensions like guidelines and transparency.

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?

Given the tool's complexity (a read operation with 2 required parameters), lack of annotations, and no output schema, the description is incomplete. It doesn't explain what information is returned (e.g., member details like name or role), potential side effects, or error conditions. For a tool that likely returns structured data about organization members, this leaves too much undefined, making it insufficient for reliable 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?

The input schema has 100% description coverage, with parameters 'organizationId' and 'memberId' documented as '组织 ID' and '成员 ID' respectively. The description adds no additional meaning beyond this, such as format examples (e.g., numeric vs. string IDs) or relationships between parameters. Since the schema already does the heavy lifting, the baseline score of 3 is appropriate, but there's no extra value from the description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Get information about a member in an organization' clearly states the verb ('Get') and resource ('member in an organization'), making the purpose understandable. However, it's vague about what specific information is retrieved (e.g., name, role, status) and doesn't distinguish it from sibling tools like 'get_organization_member_info_by_user_id' or 'list_organization_members', which handle similar member-related data. This lack of specificity and differentiation keeps it at a basic level.

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 (e.g., needing organization and member IDs), exclusions, or comparisons to siblings like 'get_organization_member_info_by_user_id' (which might use a different identifier) or 'list_organization_members' (which retrieves multiple members). Without such context, users must infer usage from the tool name alone, leading to potential confusion.

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