testit-mcp-server

create_project

Creates a new TestIT project from a payload containing at least a name, so teams can organize work items and test management under a dedicated project.

Instructions

Create a new project (payload: CreateProjectApiModel, at least name). Cloud instances may answer 402 when the plan's project limit is reached.

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": {
      "payload": "<payload>"
    },
    "name": "create_project"
  }
}

Input Schema

Name	Required	Description	Default
`payload`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0Nov 14, 2026

TDQS

B3.2/5.0

Behavior3/5

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

Annotations already declare the mutation profile (readOnly=false, destructive=false, idempotent=false, openWorld=true), so the description is not carrying the safety burden. It does add one genuinely useful behavior: cloud instances may return 402 when the plan's project limit is reached. It does not say what is returned on success or whether the caller becomes project owner.

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 short sentences with zero filler, and the core operation is front-loaded. The parenthetical payload note is slightly compressed but still readable.

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?

For a mutation tool with a free-form nested payload and no output schema, the description covers the essentials (what it creates, minimum required field, limit failure) but omits the return value and most of the payload contract. Adequate to call it, not sufficient to call it confidently.

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 coverage is 0% and the single payload parameter is an untyped nested object with additionalProperties=true, so the description must compensate. It identifies the payload model name and the one minimum field (name), which is real added value, but the remaining fields of CreateProjectApiModel remain undocumented in both description and 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?

States a specific verb and resource ("Create a new project") and names the payload model, so an agent knows exactly what happens. It does not explicitly distinguish itself from other create_* siblings (create_autotest, create_work_item), but the 'project' resource scope makes the intent unambiguous.

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 guidance on when to call this versus alternatives, no stated prerequisites (permissions, required parent scope), and no indication of what to do after creation. The only conditional information is the 402 failure mode, which is a behavior note rather than usage guidance.

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

Deploy Server