Skip to main content
Glama
mrchris2000

MCP DevOps Plan Server

by mrchris2000

get_releases

Retrieve release information for a specific application in DevOps Plan systems to track deployment status and manage software delivery.

Instructions

Get the list of releases in Plan for a given application

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
applicationYesName of the application

Implementation Reference

  • Implementation of the 'get_releases' MCP tool.
    server.tool(
        "get_releases",
        "Get the list of releases in Plan for a given application",
        {
            application: z.string().describe("Name of the application")
        },
        async ({ application }) => {
            try {
                if (!globalCookies) {
                    globalCookies = await getCookiesFromServer(serverURL);
                    if (!globalCookies) {
                        console.error("Failed to retrieve cookies from server.");
                        return { error: "Failed to retrieve cookies." };
                    }
                    console.log("Received Cookies:", globalCookies);
                } else {
                    console.log("Reusing Stored Cookies:", globalCookies);
                }
    
                const queryPayload = {
                    queryDef: {
                        primaryEntityDefName: "Release",
                        queryFieldDefs: [
                            { fieldPathName: "Name", isShown: true, sortOrder: 0 },
                            { fieldPathName: "ReleaseType", isShown: true, sortOrder: 0 },
                            { fieldPathName: "dbid", isShown: true, sortOrder: 0 },
                            { fieldPathName: "record_type", isShown: true, sortOrder: 0 },
                            { fieldPathName: "Sprints", isShown: true, sortOrder: 0 }
                        ],
                        filterNode: {
                            boolOp: "BOOL_OP_AND",
                            fieldFilters: [],
                            childFilterNodes: []
                        }
                    },
                    resultSetOptions: {
                        convertToLocalTime: false,
                        maxResultSetRows: 10000,
                        pageSize: 10000
                    }
                };
    
                const queryResponse = await fetch(`${serverURL}/ccmweb/rest/repos/${teamspaceID}/databases/${application}/query`, {
                    method: 'POST',
                    headers: {
                        'Content-Type': 'application/json',
                        'Authorization': `Basic ${personal_access_token_string}`,
                        'Cookie': globalCookies
                    },
                    body: JSON.stringify(queryPayload)
                , ...getAgentOptions(serverURL)
                });
    
                const queryData = await queryResponse.json();
                const resultSetId = queryData.result_set_id;
    
                if (!resultSetId) {
                    throw new Error(`Failed to retrieve result set ID. Response: ${JSON.stringify(queryData)}`);
                }
    
                const releasesResponse = await fetch(`${serverURL}/ccmweb/rest/repos/${teamspaceID}/databases/${application}/query/${resultSetId}`, {
                    method: 'GET',
                    headers: {
                        'Content-Type': 'application/json',
                        'Authorization': `Basic ${personal_access_token_string}`,
                        'Cookie': globalCookies
                    }
                , ...getAgentOptions(serverURL)
                });
    
                const releasesData = await releasesResponse.json();
    
                if (releasesData && releasesData.rows) {
                    return {
                        content: [{ type: 'text', text: `Releases retrieved: ${JSON.stringify(releasesData)}` }]
                    };
                } else {
                    throw new Error("Failed to retrieve releases");
                }
            } catch (e) {
                return {
                    content: [{ type: 'text', text: `Error retrieving releases: ${e.message}` }]
                };
            }
        }
    )
Behavior2/5

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

No annotations are provided, so the description carries full burden. It fails to disclose whether this is read-only, what the return format looks like, pagination behavior, or error conditions. The word 'Get' implies read access but provides no concrete behavioral guarantees.

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, front-loaded sentence with zero redundancy. Every word earns its place: action (Get), object (list of releases), context (in Plan), and filter (for a given application).

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 single-parameter retrieval tool with complete schema coverage, the description is minimally adequate. However, given the lack of output schema and annotations, it should disclose basic behavioral traits (read-only nature, return structure) to be complete.

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%, establishing a baseline of 3. The description mentions 'for a given application', acknowledging the parameter's purpose, but adds no additional semantic context such as expected format, case sensitivity, or where to obtain valid application names.

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 uses specific verb 'Get' with clear resource 'releases' and scope 'in Plan for a given application'. It distinguishes the resource from siblings like get_sprints and get_work_items by specifying 'releases', though it doesn't explicitly contrast with create_or_update_release.

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 explicit when-to-use guidance, prerequisites, or alternative selections. It does not mention that get_applications might be needed first to obtain valid application names, nor does it clarify when to query releases versus sprints or work items.

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/mrchris2000/mcp-devops-plan'

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