Skip to main content
Glama

delete_project

Remove specified projects from the CODING DevOps platform using the project ID, ensuring efficient project management and resource allocation.

Instructions

删除 CODING DevOps 中的指定项目

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
projectIdYes要删除的项目ID

Implementation Reference

  • The core handler function that executes the delete_project tool logic: initializes the CodingConnection, deletes the project by ID via API, and returns a success message.
    export async function deleteProject(args: DeleteProjectArgs, config: CodingDevOpsConfig) {
      CodingConnection.initialize(config);
      const connection = CodingConnection.getInstance();
      
    
      await connection.deleteProject({
        ProjectId: args.projectId
      });
    
      return {
        content: [
          {
            type: 'text',
            text: `Successfully deleted project with ID: ${args.projectId}`,
          },
        ],
      };
    }
  • Input schema definition for the delete_project tool, specifying the required projectId parameter.
    {
      name: 'delete_project',
      description: '删除 CODING DevOps 中的指定项目',
      inputSchema: {
        type: 'object',
        properties: {
          projectId: { 
            type: 'string', 
            description: '要删除的项目ID' 
          }
        },
        required: ['projectId'],
      }
    },
  • src/index.ts:114-115 (registration)
    Main server dispatch/registration for delete_project tool, calling the project.deleteProject handler.
    case 'delete_project':
      result = await tools.project.deleteProject(request.params.arguments);
  • Local registration of delete_project within projectTools module, exporting the handler wrapper and definitions.
    export const projectTools = {
      initialize: (config: CodingDevOpsConfig) => ({
        listProjects: (args: ListProjectsArgs) => listProjects(args, config),
        createProject: (args: CreateProjectArgs) => createProject(args, config),
        deleteProject: (args: DeleteProjectArgs) => deleteProject(args, config),
        definitions,
      }),
  • Supporting API method in CodingConnection that performs the actual HTTP request to delete the project.
    public async deleteProject(params: {
      ProjectId: string;
    }): Promise<void> {
      const requestBody = {
        Action: 'DeleteOneProject',
        ProjectId: params.ProjectId
      };
    
      await axios.post(
        `${CodingConnection.config.apiUrl}/?Action=DeleteOneProject`,
        requestBody,
        {
          headers: {
            'Authorization': `token ${CodingConnection.config.token}`,
            'Content-Type': 'application/json',
            'Accept': 'application/json'
          }
        }
      );
    }
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. It states the tool deletes a project, implying a destructive mutation, but doesn't disclose critical behavioral traits: whether deletion is permanent, if it requires specific permissions, what happens to associated resources, or error conditions. For a destructive tool with zero annotation coverage, this is a significant gap.

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 in Chinese that directly states the tool's purpose without unnecessary words. It is appropriately sized and front-loaded, with zero waste.

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 the tool's destructive nature, lack of annotations, and no output schema, the description is incomplete. It doesn't cover behavioral aspects like irreversibility, permissions, or response format. For a mutation tool with high complexity (deletion), more context is needed to ensure safe and correct usage.

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?

Schema description coverage is 100%, with the single parameter 'projectId' documented in the schema as '要删除的项目ID' (project ID to delete). The description adds no additional parameter semantics beyond this, but with only one parameter and full schema coverage, the baseline is high. No extra value is provided, but the schema suffices.

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 ('删除' meaning delete) and the resource ('CODING DevOps 中的指定项目' meaning specified project in CODING DevOps). It distinguishes from siblings like 'delete_issue' by specifying the resource type. However, it doesn't explicitly contrast with other project-related tools like 'create_project' or 'list_projects'.

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 guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., project must exist), consequences (e.g., irreversible deletion), or when to choose 'delete_project' over other project operations like 'list_projects' for verification. The context is implied but not explicit.

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