Skip to main content
Glama

Create Manual Test Suite

create_manual_test_suite

Create a test suite folder to organize manual test cases, optionally nested under a parent suite. Use it to structure test cases by feature or module before adding them.

Instructions

Create a new test suite folder for organizing manual test cases. Requires write permission. Use parentSuiteId to nest it under an existing suite — get the ID from list_manual_test_suites() first.

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

Input Schema

NameRequiredDescriptionDefault
nameYesSuite name
projectIdYesProject ID
descriptionNo
parentSuiteIdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changedv2.2.0
    • addedInput schema / $schema
      Added value: +"http://json-schema.org/draft-07/schema#"
    • addedInput schema / additionalProperties
      Added value: +false
    • removedInput schema / properties / description / description
      Removed value: -"Description of the test suite."
    • changedInput schema / properties / name / description
      Previous value: -"Suite name (Required). A descriptive name for the test suite."New value: +"Suite name"
    • addedInput schema / properties / name / maxLength
      Added value: +500
    • removedInput schema / properties / parentSuiteId / description
      Removed value: -"Optional parent suite ID to create this suite as a child of another suite. If not provided, creates a root-level suite."
    • changedInput schema / properties / projectId / description
      Previous value: -"Project ID (Required). The TestDino project identifier."New value: +"Project ID"
  2. Changed1 schema field changedv1.0.10
    • addedInput schema / properties / description
      Added value: +{
      +  "description": "Description of the test suite.",
      +  "type": "string"
      +}
  3. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and openWorldHint=false, so the mutation/safety profile is covered; the description adds the useful "Requires write permission" auth requirement. It does not disclose what happens on duplicate names, whether the new suite ID is returned, or failure behavior — meaningful gaps for a create tool that agents will chain from.

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, each doing distinct work: purpose, precondition, and parameter guidance. The core action is front-loaded with zero filler.

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?

No output schema exists, so the description is the only place an agent could learn what a successful call returns (e.g., the new suite's ID for follow-up case creation) — and it is silent on that. For a chained create operation with two undocumented optional params, this leaves a gap.

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

Parameters4/5

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

With only 50% schema description coverage, the description carries real weight: it explains that parentSuiteId nests the folder under an existing suite and where to source that ID. The optional description parameter is still unexplained, but the guidance on the non-obvious nesting parameter exceeds the schema baseline.

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 gives a specific verb and resource ("Create a new test suite folder") and clarifies its role as a container "for organizing manual test cases," which implicitly separates it from create_manual_test_case. It does not explicitly name a sibling it is not, so differentiation is inferable rather than stated.

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

Usage Guidelines4/5

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

It gives a concrete conditional instruction for nesting via parentSuiteId and routes the agent to list_manual_test_suites() to obtain the ID, which is a real alternative-tool pointer. It stops short of stating when a top-level suite is preferable or any exclusions.

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