Skip to main content
Glama

Create Test Case

create_test_case

Create a structured test case in Allure TestOps, including steps with expected results, tags, attachments, and custom fields for issue tracking.

Instructions

Create a new test case in Allure TestOps.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesThe name of the test case.
tagsNoList of tag names.
stepsNoList of steps. Each step must be a dict with 'action' and 'expected' keys. Example: [{'action': 'Login', 'expected': 'Dashboard visible'}]
issuesNoOptional list of issue keys to link (e.g., ['PROJ-123']).
project_idNoOptional override for the default Project ID.
attachmentsNoList of attachments.Example Base64: [{'name': 's.png', 'content': '<base64>', 'content_type': 'image/png'}]Example URL: [{'name': 'report.pdf', 'url': 'http://example.com/report.pdf', 'content_type': 'application/pdf'}]
descriptionNoA markdown description of the test case.
custom_fieldsNoDictionary of custom field names and their values (string or list of strings).Example: {'Layer': 'UI', 'Components': ['Auth', 'DB']}
output_formatNoOutput format: 'json' (default) or 'plain'.
test_layer_idNoOptional test layer ID to assign (use list_test_layers to find IDs). If provided, the layer must exist in the project.
integration_idNoOptional integration ID for issue linking (use list_integrations to find IDs). Required when multiple integrations exist. Mutually exclusive with integration_name.
test_layer_nameNoOptional test layer name to assign (exact case-sensitive match). Mutually exclusive with test_layer_id.
integration_nameNoOptional integration name for issue linking (exact case-sensitive match). Required when multiple integrations exist. Mutually exclusive with integration_id.
Behavior2/5

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

The description does not add behavioral context beyond what annotations provide. Annotations indicate readOnlyHint=false and destructiveHint=false, but the description does not clarify idempotency, side effects (e.g., duplication behavior), or required permissions. For a creation tool, this is a gap.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single concise sentence, but given the tool's 13 parameters and complexity, a slightly more structured description (e.g., indicating key optional parameters) would improve usability without adding verbosity.

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

Completeness2/5

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

Despite the schema being rich, the description fails to provide high-level context about return values, common use cases, or relationships with sibling tools (e.g., using 'list_test_cases' to verify creation). The lack of output schema makes this gap more significant.

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%, with detailed descriptions for each parameter (e.g., examples for steps and attachments). The tool description itself does not add parameter-level meaning, so baseline 3 applies.

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 clearly states the action ('Create'), the resource ('test case'), and the system ('Allure TestOps'). It distinguishes this tool from sibling tools like 'update_test_case' or 'delete_test_case' by specifying the creation operation.

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?

The description lacks any guidance on when to use this tool versus alternatives, such as 'update_test_case' or when to use different parameter combinations. No prerequisites or contextual hints are provided.

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/ivanostanin/lucius-mcp'

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