Skip to main content
Glama
aliyun

AlibabaCloud DevOps MCP Server

Official
by aliyun

get_organization_role

Retrieve role details and permissions for users in Alibaba Cloud DevOps organizations to manage access control and team responsibilities.

Instructions

[Organization Management] Get information about an organization role

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
organizationIdYesOrganization ID
roleIdYesRole ID

Implementation Reference

  • Tool handler implementation: parses input arguments using the schema, calls the core getOrganizationRoleFunc, and returns the role as JSON string.
    case "get_organization_role": {
      const args = types.GetOrganizationRoleSchema.parse(request.params.arguments);
      const role = await organization.getOrganizationRoleFunc(
        args.organizationId,
        args.roleId
      );
      return {
        content: [{ type: "text", text: JSON.stringify(role, null, 2)}]
      }
    }
  • Core helper function that makes the API request to fetch the organization role and parses the response with OrganizationRoleSchema.
    export async function getOrganizationRoleFunc(
        organizationId: string,
        roleId: string
    ): Promise<z.infer<typeof OrganizationRoleSchema>> {
        const url = `/oapi/v1/platform/organizations/${organizationId}/roles/${roleId}`;
    
        const response = await yunxiaoRequest(url, {
            method: "GET"
        });
    
        return OrganizationRoleSchema.parse(response);
    }
  • Tool registration defining the name, description, and input schema.
      name: "get_organization_role",
      description: "[Organization Management] Get information about an organization role",
      inputSchema: zodToJsonSchema(types.GetOrganizationRoleSchema),
    },
  • Input schema for the tool defining organizationId and roleId parameters.
    export const GetOrganizationRoleSchema = z.object({
      organizationId: z.string().describe("Organization ID"),
      roleId: z.string().describe("Role ID")
    });
  • Output schema defining the structure of the organization role object.
    export const OrganizationRoleSchema = z.object({
      id: z.string().describe("Role ID"),
      name: z.string().describe("Role name"),
      organizationId: z.string().describe("Organization ID"),
      permissions: z.array(z.string()).describe("Role permission list")
    });
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[s] information,' implying a read-only operation, but doesn't clarify aspects like authentication requirements, rate limits, error handling, or response format. This leaves gaps in understanding how the tool behaves in practice.

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 with zero waste. It's front-loaded with the core purpose ('Get information about an organization role') and includes a bracketed context hint ('[Organization Management]') that adds value without verbosity.

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

Completeness3/5

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

Given the tool's complexity (simple read operation with 2 parameters) and no annotations or output schema, the description is minimally adequate. It states the purpose but lacks details on behavior, usage context, or return values. For a basic 'get' tool, this is acceptable but leaves room for improvement in guiding the agent.

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 ('organizationId' and 'roleId') documented in the schema. The description adds no additional meaning beyond the schema, such as explaining how to obtain these IDs or their relationships. Baseline score of 3 is appropriate since the schema handles parameter documentation adequately.

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: 'Get information about an organization role.' It specifies the verb ('Get') and resource ('organization role'), making the action clear. However, it doesn't distinguish this tool from its sibling 'list_organization_roles' (which likely lists multiple roles), so it misses full differentiation.

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 'list_organization_roles' for listing roles or 'get_organization_member_info' for related data, nor does it specify prerequisites such as needing specific permissions or organizational 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/aliyun/alibabacloud-devops-mcp-server'

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