Skip to main content
Glama
aliyun

AlibabaCloud DevOps MCP Server

Official
by aliyun

get_organization_department_ancestors

Retrieve the hierarchical chain of parent departments for a specific department within an Alibaba Cloud DevOps organization to understand reporting structures and access controls.

Instructions

Get the ancestors of a department in an organization

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
organizationIdYesOrganization ID
idYesDepartment ID

Implementation Reference

  • MCP tool handler for get_organization_department_ancestors: parses input args using schema, calls the core helper function, and formats response as JSON text.
    case "get_organization_department_ancestors": {
      const args = types.GetOrganizationDepartmentAncestorsSchema.parse(request.params.arguments);
      const ancestors = await organization.getOrganizationDepartmentAncestorsFunc(
        args.organizationId,
        args.id
      );
      return {
        content: [{ type: "text", text: JSON.stringify(ancestors, null, 2) }],
      };
    }
  • Zod schema defining input parameters: organizationId and department id.
    export const GetOrganizationDepartmentAncestorsSchema = z.object({
      organizationId: z.string().describe("Organization ID"),
      id: z.string().describe("Department ID"),
    });
  • Tool registration entry with name, description, and JSON schema derived from Zod schema.
    {
      name: "get_organization_department_ancestors",
      description: "Get the ancestors of a department in an organization",
      inputSchema: zodToJsonSchema(types.GetOrganizationDepartmentAncestorsSchema),
    },
  • Helper function that constructs API URL, makes GET request to fetch department ancestors, and parses response using schema.
    export async function getOrganizationDepartmentAncestorsFunc(
        organizationId: string,
        id: string): Promise<z.infer<typeof OrganizationDepartmentsSchema>>  {
      const url = `/oapi/v1/platform/organizations/${organizationId}/departments/${id}/ancestors`;
      const response = await yunxiaoRequest(url, {
        method: "GET",
      })
      return OrganizationDepartmentsSchema.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 a read operation ('Get'), implying it's likely safe, but doesn't mention any behavioral traits such as permissions required, rate limits, error conditions, or what the output format might be (e.g., list of ancestors). This is a significant gap for a tool with no annotation coverage.

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 any unnecessary words. It's appropriately sized and front-loaded, making it easy to understand at a glance with zero waste.

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 complexity of a hierarchical query tool with no annotations and no output schema, the description is incomplete. It doesn't explain what 'ancestors' means in this context (e.g., parent departments up to the root), the return format, or any prerequisites. For a tool that likely returns structured data, this leaves significant gaps in understanding.

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 both parameters ('organizationId' and 'id') clearly documented in the schema. The description doesn't add any meaning beyond this, such as explaining how these IDs are obtained or their format. Given the high schema coverage, a baseline score of 3 is appropriate as the schema does the heavy lifting.

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' and the resource 'ancestors of a department in an organization', making the purpose specific and understandable. However, it doesn't explicitly distinguish this tool from sibling tools like 'get_organization_department_info' or 'list_organization_departments', which might handle related department data, so it misses full sibling 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. For example, it doesn't clarify if this is for hierarchical navigation compared to general department info tools like 'get_organization_department_info', or when ancestors are needed over other department-related operations. This lack of context leaves usage unclear.

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