Skip to main content
Glama
TCSoftInc

TestCollab MCP Server

by TCSoftInc

create_test_case

Create a new test case with title, steps, priority, tags, and custom fields in TestCollab to manage test scenarios efficiently.

Instructions

Create a new test case in TestCollab. Tip: Call get_project_context first to resolve suite/tag/custom field names to IDs.

Required: title Optional: project_id, suite (ID or title), description, priority (0=Low, 1=Normal, 2=High), steps, tags, requirements, custom_fields, attachments

Steps format: [{ "step": "action", "expected_result": "result" }]

Custom fields format: [{ "id": 5, "name": "field_name", "value": "value", "valueLabel": "display" }]

Example: { "title": "Verify login", "priority": 2, "steps": [ { "step": "Navigate to login", "expected_result": "Page loads" }, { "step": "Enter credentials", "expected_result": "Login succeeds" } ] }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idNoProject ID (optional if TC_DEFAULT_PROJECT is set)
titleYesTest case title (required)
suiteNoSuite ID or suite title
descriptionNoTest case description (HTML supported)
priorityNoPriority: 0=Low, 1=Normal, 2=High
stepsNoArray of test steps
tagsNoArray of tag IDs or names
requirementsNoArray of requirement IDs or names
custom_fieldsNoArray of custom field values (id optional if name provided)
attachmentsNoArray of attachment file IDs
Behavior3/5

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

With no annotations, the description carries the full burden. It correctly indicates a creation operation (write) but does not disclose any side effects, permissions needed, or the response format. The description is adequate but could be more transparent about what happens after creation.

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?

The description is fairly concise given the complexity (10 parameters). It front-loads the purpose, then groups required/optional, and provides structured examples. Minor redundancy exists but overall efficient.

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?

Given the tool's complexity (10 params, no output schema), the description covers parameters, formats, and a cross-tool tip. It lacks what the response will be (e.g., created test case ID), but still provides sufficient context for correct invocation.

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?

Input schema coverage is 100%, so baseline is 3. The description adds significant value by providing step and custom field formats, an example usage, and clarifying that suite can be an ID or title. This enriches the semantic understanding beyond the schema.

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 explicitly states 'Create a new test case in TestCollab.' This is a specific verb-resource pair that clearly distinguishes it from sibling tools like create_suite or create_test_plan.

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?

The description includes a helpful tip to call get_project_context first to resolve names to IDs, providing clear usage guidance. It also lists required and optional parameters. However, it does not explicitly contrast with alternatives like update_test_case or state when not to use this tool.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/TCSoftInc/testcollab-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server