Skip to main content
Glama
mrchris2000

MCP DevOps Plan Server

by mrchris2000

get_sprints

Retrieve the list of sprints for a specific application in DevOps Plan systems to track development cycles and project progress.

Instructions

Get the list of sprints in Plan for a given application

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
applicationYesName of the application

Implementation Reference

  • The implementation of the `get_sprints` tool, which queries the Plan server for sprints.
    server.tool(
        "get_sprints",
        "Get the list of sprints 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: "Sprint",
                        queryFieldDefs: [
                            { fieldPathName: "Name", isShown: true, sortOrder: 0 },
                            { fieldPathName: "StartDate", isShown: true, sortOrder: 0 },
                            { fieldPathName: "EndDate", isShown: true, sortOrder: 0 },
                            { fieldPathName: "dbid", isShown: true, sortOrder: 0 },
                            { fieldPathName: "record_type", 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 sprintsResponse = 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 sprintsData = await sprintsResponse.json();
    
                if (sprintsData && sprintsData.rows) {
                    return {
                        content: [{ type: 'text', text: `Sprints retrieved: ${JSON.stringify(sprintsData)}` }]
                    };
                } else {
                    throw new Error("Failed to retrieve sprints");
                }
            } catch (e) {
                return {
                    content: [{ type: 'text', text: `Error retrieving sprints: ${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 the full burden of behavioral disclosure. While 'Get' implies a read-only operation, the description fails to specify error handling (what happens if the application is invalid), whether the results are paginated, or the structure/format of the returned sprint data.

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 of 10 words with the action verb front-loaded. There is no redundant or wasted language; every word contributes to defining the tool's scope.

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 low complexity (one required string parameter) and complete schema coverage, the description is minimally adequate. However, since no output schema exists, the description should ideally describe the return format (e.g., 'returns a list of sprint objects') or what constitutes a sprint in this context, which it omits.

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?

With 100% schema description coverage for the single 'application' parameter, the schema already documents the input sufficiently. The description adds minimal semantic context by framing it as 'for a given application,' but does not provide examples, validation constraints, or format details beyond the schema.

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 action ('Get the list'), resource ('sprints in Plan'), and scope ('for a given application'). The verb 'Get' implicitly distinguishes this from the sibling 'create_or_update_sprint', though it does not explicitly mention the sibling or clarify whether this retrieves active, closed, or all sprints.

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?

There is no guidance on when to use this tool versus alternatives like 'get_work_items' or 'get_releases', nor are there prerequisites mentioned (e.g., whether the application must exist or be accessible). The description assumes the user knows what 'Plan' refers to without 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/mrchris2000/mcp-devops-plan'

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