testit-mcp-server

list_sections

Read-only

Retrieve all project sections as a flat list with parent IDs, so you can identify section IDs for creating work items.

Instructions

List all sections (folders) of a project as a flat list with parentId. The root section has parentId=null. Use section IDs as sectionId when creating work items.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_sections"
  }
}

Input Schema

Name	Required	Description
`page`	No	1-based page number; alternative to skip. Uses "size" (default 50).
`size`	No	Page size for "page"; alias of take.
`skip`	No	Number of items to skip (offset).
`take`	No	Max number of items to return.
`orderBy`	No	Sort expression, e.g. "createdDate desc".
`projectId`	No
`projectName`	No
`searchField`	No	Field name to search in.
`searchValue`	No	Value to search for in searchField.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0Nov 14, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered. The description adds genuinely useful behavioral context beyond that: results are returned flat rather than nested, and the root section is signalled by parentId=null, which is a convention the agent cannot infer from the schema. It omits pagination defaults and whether the full tree is always 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?

Three short sentences with zero filler; the core behavior and the result shape are front-loaded, and the downstream hint comes last. Every sentence carries information.

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 9-parameter read-only list tool with no output schema, the definition covers the essential return shape and the root-section convention. It leaves out pagination behavior (defaults, aliases) and project-selector semantics, which are the main things an agent could get wrong when invoking it.

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 78%, so the schema already documents most parameters and the baseline is 3. The description adds the 'of a project' scoping notion but does not disambiguate the two project selectors (projectId vs projectName) or relate the page/size vs skip/take pagination aliases, leaving the highest-risk ambiguity unresolved.

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 names a specific verb and resource ('List all sections (folders) of a project') and clarifies the shape of the result ('flat list with parentId'), which distinguishes it from create_section and from tree-shaped section endpoints. It stops short of naming an explicit alternative, but the purpose is unambiguous.

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?

Guidance is present but downstream-oriented: 'Use section IDs as sectionId when creating work items' tells the agent why it would want sections, which implies when to call it. There is no explicit when-not guidance, no mention of the sibling create_section, and no note about which of projectId/projectName to supply.

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

Deploy Server