Retrieve complete details of a specific merge request by its local ID, including repository and organization context, for efficient change management.
[Code Management] Get detailed information about a specific change request (merge request) by its local ID.
| Name | Required | Description | Default |
|---|---|---|---|
| localId | Yes | 局部ID，表示代码库中第几个合并请求。示例：'1' 或 '42' | |
| repositoryId | Yes | 代码库ID或全路径(斜杠须编码为%2F)，如 2835387 或 myorg%2FmyRepo | |
| organizationId | Yes | 组织ID |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
v0.3.60Input schema / $schemaRemoved value: -"http://json-schema.org/draft-07/schema#"Input schema / properties / localId / typePrevious value: -"string"New value: +[
+ "string",
+ "number"
+]Input schema / properties / organizationId / descriptionPrevious value: -"组织ID，可在组织管理后台的基本信息页面获取。示例：'60d54f3daccf2bbd6659f3ad'"New value: +"组织ID"Input schema / properties / repositoryId / descriptionPrevious value: -"代码库ID或者URL-Encoder编码的全路径。示例：'2835387' 或 '60de7a6852743a5162b5f957%2FDemoRepo'（注意：斜杠需要URL编码为%2F）"New value: +"代码库ID或全路径(斜杠须编码为%2F)，如 2835387 或 myorg%2FmyRepo"Input schema / properties / repositoryId / typePrevious value: -"string"New value: +[
+ "string",
+ "number"
+]v0.3.35Input schema / properties / localId / descriptionPrevious value: -"Local ID, represents the nth merge request in the repository"New value: +"局部ID，表示代码库中第几个合并请求。示例：'1' 或 '42'"Input schema / properties / organizationId / descriptionPrevious value: -"Organization ID, can be found in the basic information page of the organization admin console"New value: +"组织ID，可在组织管理后台的基本信息页面获取。示例：'60d54f3daccf2bbd6659f3ad'"Input schema / properties / repositoryId / descriptionPrevious value: -"Repository ID or a combination of organization ID and repository name, for example: 2835387 or organizationId%2Frepo-name (Note: slashes need to be URL encoded as %2F)"New value: +"代码库ID或者URL-Encoder编码的全路径。示例：'2835387' 或 '60de7a6852743a5162b5f957%2FDemoRepo'（注意：斜杠需要URL编码为%2F）"v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, and the description offers no additional behavioral details beyond the verb 'get'. It does not state that the operation is read-only, mention side effects, permissions, or error conditions, leaving the burden on the description entirely unmet.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, concise sentence with no unnecessary words. It directly states the purpose without fluff.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple get operation with well-described parameters and no output schema, the description is sufficient. It clearly identifies the resource and action, though it does not elaborate on the return structure or possible error cases, which is acceptable given the simplicity.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The schema descriptions for all three parameters are clear and complete (100% coverage). The tool description adds no extra meaning to the parameters; it only refers to 'its ID', which could ambiguously map to any of the three. Since schema coverage is high, baseline of 3 is appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the action (get) and the resource (change request/merge request) with a specific identifier. It distinguishes from sibling tools like list_change_requests by indicating it retrieves detailed information for a single item.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies usage for fetching a single change request by ID, but it does not explicitly mention when not to use it or contrast with alternatives such as list_change_requests. Guidance is only inferred from the verb and parameter.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
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