Skip to main content
Glama
mrchris2000

MCP DevOps Plan Server

by mrchris2000

get_applications

Retrieve all applications from the DevOps Plan system to manage and view available software projects and components.

Instructions

Retrieves all applications from the Plan system

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The implementation of the get_applications tool, which retrieves applications by querying the Plan system's databases API endpoint.
    server.tool(
        "get_applications",
        "Retrieves all applications from the Plan system",
        {},
        async () => {
            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); // Print cookies after receiving
                } else {
                    console.log("Reusing Stored Cookies:", globalCookies); // Print when reusing stored cookies
                }
                const response = await fetch(`${serverURL}/ccmweb/rest/repos/${teamspaceID}/databases`, {
                    method: 'GET',
                    headers: {
                        'Content-Type': 'application/json',
                        'Accept': 'application/json',
                        'Authorization': `Basic ${personal_access_token_string}`,
                        'Cookie': globalCookies
                    }
                });
    
                const data = await response.json();
    
                if (data && Array.isArray(data)) {
                    const applications = data.map(app => ({
                        id: app.dbId,
                        applicationName: app.name
                    }));
    
                    return {
                        content: [
                            { type: 'text', text: `Applications retrieved: ${JSON.stringify(applications)}` }
                        ]
                    };
                } else {
                    throw new Error("Failed to retrieve applications");
                }
            } catch (e) {
                return {
                    content: [{ type: 'text', text: `Error retrieving applications: ${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 'Retrieves' implies a read-only operation, the description lacks critical details: pagination behavior for large result sets, return format (array vs object), authentication requirements, or rate limiting concerns. It does not compensate for the missing annotations.

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 with no redundant words. The core action and resource are front-loaded, making it immediately scannable.

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 simplicity (no parameters) and lack of output schema, the description provides minimal viable context. However, it omits what the tool returns (e.g., 'returns a list of applications') and whether the result set might be large. For a retrieval tool with no schema coverage burdens, this is adequate but incomplete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema contains zero parameters. Per evaluation rules, zero-parameter tools receive a baseline score of 4. The description implicitly confirms no filtering is possible by stating 'all applications', which aligns with the empty 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 verb (Retrieves), scope (all), and resource (applications) within the Plan system domain. It distinguishes from siblings like get_work_items and get_releases by targeting 'applications' specifically, though it assumes familiarity with what constitutes an 'application' in this context.

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?

No guidance provided on when to use this tool versus siblings like get_available_projects or get_available_components. Given the similar 'get_available_*' naming patterns in siblings, the description fails to clarify whether applications are user-specific, workspace-scoped, or how they relate to 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/mrchris2000/mcp-devops-plan'

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