Skip to main content
Glama
mrchris2000

MCP DevOps Plan Server

by mrchris2000

delete_work_item

Remove a work item from DevOps Plan systems by specifying its unique identifier and application name to maintain clean project records.

Instructions

Deletes a work item in Plan

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dbidYesThe dbid field from the workitem to identify it, this is the first field returned for each workitem in the get_work_items tool.
applicationYesName of the application

Implementation Reference

  • The handler function that executes the DELETE request to remove a work item.
    async ({ dbid, 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); // 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/${application}/records/WorkItem/${dbid}?actionName=Delete&useDbid=true`, {
                method: 'DELETE',
                headers: {
                    'Content-Type': 'application/json',
                    'Authorization': `Basic ${personal_access_token_string}`,
                    'Cookie': globalCookies
                }
            });
    
            if (response.ok) {
                return {
                    content: [{ type: 'text', text: `Work item ${dbid} deleted successfully` }]
                };
            } else {
                throw new Error("Failed to delete work item");
            }
        } catch (e) {
  • old-server.js:533-539 (registration)
    MCP tool registration for 'delete_work_item'.
    server.tool(
        "delete_work_item",
        "Deletes a work item in Plan",
        {
            dbid: z.string().describe("The dbid field from the workitem to identify it, this is the first field returned for each workitem in the get_work_items tool."),
            application: z.string().describe("Name of the application")
        },
Behavior2/5

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

No annotations provided, so description carries full burden. While 'Deletes' implies destruction, it fails to disclose whether deletion is permanent/irreversible, if it cascades to child items, or required permissions. Lacks critical safety context for a destructive operation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Extremely brief (4 words) and front-loaded with the action. Efficient but arguably too terse given the destructive nature and absence of annotations; could accommodate one safety clause without losing conciseness.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Inadequate for a destructive 2-parameter tool with no output schema. Description omits destructive confirmation, success/failure behavior, and whether the operation is recoverable. Schema covers inputs but description fails to cover behavioral outputs.

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 has 100% description coverage, documenting both dbid and application thoroughly. Description adds no parameter-specific context, but baseline 3 is appropriate when schema does the heavy lifting.

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?

Clear verb ('Deletes') and resource ('work item'), though 'in Plan' is slightly ambiguous (product name vs. generic planning). Distinguishes from siblings by action type but doesn't clarify delete vs. update/change-state scenarios.

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?

Provides no guidance on when to use deletion versus alternatives like update_work_item or change_work_item_state. No mention of prerequisites (e.g., required work item states) or cascading effects on related entities.

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