Skip to main content
Glama
Sign In
codearts-req

codearts-req

by anfang2077-glitch
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

create_project

Creates a Huawei Cloud CodeArts project with a required name and type, returning project IDs and metadata for project-management workflows.

Instructions

创建华为云 CodeArts 需求项目（POST /v4/project）。返回 project_id、project_num_id、project_name、project_type、user_num_id。

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "project_name": "<project_name>",
      "project_type": "<project_type>"
    },
    "name": "create_project"
  }
}

Input Schema

NameRequiredDescriptionDefault
sourceNo项目来源，选填，0-64 字符
descriptionNo项目描述，选填
template_idNo项目模板 ID，选填：10001/10002/10003；project_type=ipd 时必传
project_nameYes项目名称，必填，1-128 字符
project_typeYes项目类型，必填：scrum/normal/xboard/basic/phoenix/ipd
enterprise_idNo企业项目 ID，选填

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.2/5.0
Behavior3/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 does disclose the HTTP method (POST), which makes the mutation nature clear, and it enumerates the returned identifiers (project_id, project_num_id, etc.). However, it says nothing about permission requirements, side effects, idempotency, or what happens on duplicate names, leaving meaningful gaps for a write 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?

Two compact sentences with the action and endpoint front-loaded and no filler. The return-field enumeration is slightly dense but serves a purpose given the absence of an output schema.

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?

The description compensates for the missing output schema by naming the returned fields, and the schema itself fully documents the six inputs. What remains missing is behavioral context for a mutation tool with no annotations: prerequisites, failure modes, and how it relates to list_projects.

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%, so every parameter, including the conditional template_id rule for ipd projects, is already documented in the schema. The description adds no parameter-level meaning beyond that; the return-field list is the only extra information.

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 states a specific verb and resource ('创建华为云 CodeArts 需求项目') and adds the underlying endpoint (POST /v4/project), so an agent immediately knows this is a project-creation call rather than a read. It does not explicitly name the sibling list_projects, but the create-versus-list distinction is obvious from the wording.

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 when-to-use guidance, no mention of prerequisites such as authentication or an existing enterprise/template context, and no comparison with list_projects. The only implicit signal is that creation is a distinct action from listing.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools