Skip to main content
Glama
aliyun

AlibabaCloud DevOps MCP Server

Official
by aliyun

get_project

Retrieve detailed information about a specific Yunxiao DevOps project by providing its organization ID and project identifier.

Instructions

[Project Management] Get information about a Yunxiao project

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
organizationIdYesOrganization ID
idYesProject unique identifier

Implementation Reference

  • The main handler for the 'get_project' tool. Parses input arguments using GetProjectSchema, calls the underlying getProjectFunc helper to fetch project details via API, and returns the JSON-formatted project information.
    case "get_project": {
      const args = types.GetProjectSchema.parse(request.params.arguments);
      const projectInfo = await project.getProjectFunc(
        args.organizationId,
        args.id
      );
      return {
        content: [{ type: "text", text: JSON.stringify(projectInfo, null, 2) }],
      };
    }
  • Zod schema definition for 'get_project' tool input validation: requires organizationId and project id.
    export const GetProjectSchema = z.object({
      organizationId: z.string().describe("Organization ID"),
      id: z.string().describe("Project unique identifier"),
    });
  • Tool registration object defining name, description, and input schema for 'get_project' within the getProjectManagementTools array, which is included in the PROJECT_MANAGEMENT toolset.
      name: "get_project",
      description: "[Project Management] Get information about a Yunxiao project",
      inputSchema: zodToJsonSchema(types.GetProjectSchema),
    },
  • Core helper function that performs the actual API call to retrieve project information using Yunxiao's projex API and validates the response with ProjectInfoSchema.
    export async function getProjectFunc(
      organizationId: string,
      id: string
    ): Promise<z.infer<typeof ProjectInfoSchema>> {
      const url = `/oapi/v1/projex/organizations/${organizationId}/projects/${id}`;
    
      const response = await yunxiaoRequest(url, {
        method: "GET",
      });
    
      return ProjectInfoSchema.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 for behavioral disclosure. It states this is a 'Get' operation, implying read-only behavior, but doesn't clarify permissions, rate limits, error conditions, or what happens if parameters are invalid. The description adds minimal context beyond the basic operation type.

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 gets straight to the point with no wasted words. It's appropriately sized for a simple retrieval tool and front-loads the essential information.

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?

For a simple read operation with 2 parameters and 100% schema coverage, the description is minimally adequate. However, with no annotations and no output schema, it should ideally provide more context about what information is returned, error handling, or authentication requirements. The description meets basic needs but leaves gaps in behavioral context.

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 doesn't add any parameter-specific information beyond what's in the schema. According to scoring rules, when schema coverage is high (>80%), the baseline is 3 even with no param info in description.

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 with 'Get information about a Yunxiao project', specifying both the verb ('Get') and resource ('Yunxiao project'). It distinguishes from siblings like 'search_projects' by focusing on retrieving specific project details rather than searching. However, it doesn't explicitly mention what type of information is retrieved.

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 like 'search_projects' or 'get_work_item'. It doesn't mention prerequisites, such as needing both organizationId and id parameters, or contextual factors like when detailed project info is needed versus a list of projects.

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