Skip to main content
Glama
Sign In
testit-mcp-server

testit-mcp-server

by iampopovich
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

move_section

Idempotent

Move a section, including its work items and subsections, under a new parent and optionally insert it before a specified sibling section.

Instructions

Move a section (with its work items and subsections) under another parent. Optionally place it before nextSectionId.

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": {
      "id": "<id>",
      "parentId": "<parentId>"
    },
    "name": "move_section"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesSection UUID to move.
parentIdYesNew parent section UUID.
nextSectionIdNoSibling to insert before (optional).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.8/5.0
Behavior3/5

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

The annotations already establish that this is a non-destructive, idempotent mutation. The description adds meaningful context by stating that work items and subsections move along with the section, which is a cascading effect the annotations do not convey. However, it says nothing about the permissions required, what happens if parentId creates a cycle, or what is returned.

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?

Two sentences with zero waste. The primary operation is front-loaded, and the optional parameter is introduced in the second sentence.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple three-parameter mutation with full annotation coverage and no output schema, the description only needs to say what moves and where. The cascade behavior is a valuable addition. Some details, such as ordering semantics or constraints on parentId, are left to inference, but they are minor gaps.

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 100%, so the schema already documents all three parameters. The description adds only a small amount of semantic meaning about how nextSectionId is used as an optional insertion point relative to an existing sibling. The baseline score of 3 is appropriate when the schema does the heavy lifting.

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

Purpose5/5

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

The description names a specific verb (move) and resource (section) and defines the scope precisely: the section along with its work items and subsections is relocated under a new parent. It is clearly distinguishable from siblings like move_work_item and rename_section.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies its usage context and tells the agent the move is a reparenting operation, but it offers no explicit when-to-use or when-not-to-use guidance relative to alternatives. There is also no mention of prerequisites such as needing the target parent to exist in the same project.

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