testit-mcp-server

create_section

Creates a TestIT section under a project, defaulting parentId to the root section so requests avoid rejected null parents. Provide a name and optional parent, project, and pre/postcondition steps.

Instructions

Create a section. parentId defaults to the project's root section (TestIT rejects parentId=null).

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

Input Schema

Name	Required	Description
`name`	Yes
`parentId`	No	Parent section UUID (default: root section).
`projectId`	No	Project UUID (defaults to TESTIT_PROJECT_ID).
`projectName`	No
`preconditionSteps`	No
`postconditionSteps`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0Nov 14, 2026

TDQS

B3/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false and openWorldHint=true, so the mutation and non-idempotent semantics are covered. The description adds genuinely new operational context — that TestIT rejects parentId=null so it must fall back to the root section — but says nothing about permissions, name collisions, or what the created object returns.

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 the core action front-loaded and the caveat second; nothing is wasted. The parenthetical is slightly awkward but carries real information about the API's rejection of null.

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 6-parameter creation tool with no output schema, the description covers only the parentId fallback. The nested precondition/postcondition step objects and the projectName parameter remain unexplained, though annotations do relieve the burden of stating safety behavior.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 33%: parentId, projectId and name are documented, but projectName and the preconditionSteps/postconditionSteps arrays are undocumented in both schema and description. The description's parentId note largely restates the schema's 'default: root section' rather than compensating for the gaps.

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 ('Create a section'), which is unambiguous on its own. It does not distinguish this from neighbors like create_test_suite or create_project, so an agent must rely on the name to decide it is not creating a suite.

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 use this versus alternatives (create_test_suite, create_project) and no stated prerequisites such as required permissions or whether the name must be unique within the project. Only the parentId default is explained.

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

Deploy Server