Skip to main content
Glama

delete_issue

Remove work items from CODING DevOps projects by specifying the issue code and project name using the delete_issue tool on the MCP server.

Instructions

删除工作项

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
issueCodeYes事项编号
projectNameYes项目名称

Implementation Reference

  • Core handler function for the 'delete_issue' tool. Validates input parameters, initializes the CodingConnection, calls the API to delete the issue, and returns a formatted MCP response with success message.
    export async function deleteIssue(args: { 
      projectName: string;
      issueCode: number;
    }, config: CodingDevOpsConfig) {
      if (!args.projectName) {
        throw new McpError(ErrorCode.InvalidParams, 'projectName02 is required');
      }
      if (!args.issueCode) {
        throw new McpError(ErrorCode.InvalidParams, 'Issue code is required');
      }
    
      CodingConnection.initialize(config);
      const connection = CodingConnection.getInstance();
      
      await connection.deleteIssue({
        projectName: args.projectName,
        issueCode: args.issueCode
      });
    
      return {
        content: [
          {
            type: 'text',
            text: `Successfully deleted issue ${args.issueCode} in project ${args.projectName}`,
          },
        ],
      };
    }
  • Schema definition for the 'delete_issue' tool, specifying input parameters projectName (string) and issueCode (number) as required.
    {
      name: 'delete_issue',
      description: '删除工作项',
      inputSchema: {
        type: 'object',
        properties: {
          projectName: {
            type: 'string',
            description: '项目名称',
          },
          issueCode: {
            type: 'number',
            description: '事项编号',
          }
        },
        required: ['projectName', 'issueCode'],
      }
    },
  • src/index.ts:124-126 (registration)
    Registration of the 'delete_issue' tool handler in the main MCP CallToolRequest switch statement, routing calls to tools.issue.deleteIssue.
    case 'delete_issue':
      result = await tools.issue.deleteIssue(request.params.arguments);
      break;
  • Helper method in CodingConnection class that sends the HTTP POST request to the CODING DevOps API to delete the specified issue.
    public async deleteIssue(params: {
      projectName: string;
      issueCode: number;
    }): Promise<void> {
      const requestBody = {
        Action: 'DeleteIssue',
        ProjectName: params.projectName,
        IssueCode: params.issueCode
      };
    
      await axios.post(
        CodingConnection.config.apiUrl,
        requestBody,
        {
          headers: {
            'Authorization': `token ${CodingConnection.config.token}`,
            'Content-Type': 'application/json',
            'Accept': 'application/json'
          }
        }
      );
    }
  • src/index.ts:61-65 (registration)
    Initialization of tool instances, including issueTools which provides the deleteIssue handler and its schema definitions.
    const toolInstances = {
      issue: issueTools.initialize(this.config),
      project: projectTools.initialize(this.config),
      code: codeTools.initialize(this.config),
    };
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. '删除' (delete) implies a destructive mutation, but the description doesn't specify whether deletion is permanent, requires specific permissions, has confirmation steps, or what happens to related data. This is inadequate for a destructive operation with zero annotation coverage.

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 extremely concise with just three characters in Chinese ('删除工作项'), which translates to 'delete work item'. It's front-loaded with the core action and resource, with zero wasted words. This is appropriate conciseness for a simple tool.

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?

Given this is a destructive mutation tool with no annotations and no output schema, the description is incomplete. It doesn't explain what constitutes successful deletion, error conditions, return values, or system behavior. For a tool that permanently removes data, this level of documentation is insufficient.

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%, with both parameters (issueCode and projectName) documented in the schema. The description adds no additional parameter information beyond what the schema provides. According to guidelines, when schema coverage is high (>80%), the baseline score is 3 even with no param info in the description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description '删除工作项' (delete work item) states a clear verb+resource action, but it's vague about what constitutes a 'work item' and doesn't distinguish from sibling tools like delete_project. It's better than a tautology but lacks specificity about the resource being deleted.

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 is provided about when to use this tool versus alternatives like delete_project or list_issues. The description doesn't mention prerequisites, conditions for successful deletion, or what happens after deletion. It's a basic statement with no contextual usage information.

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

Related 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/yupengfei1209/coding_devops_mcp_server'

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