Skip to main content
Glama

Create Test Case

create_test_case

Create a new test case in Allure TestOps with a name, optional steps, tags, description, attachments, custom fields, and linked issues to organize and document your testing scenarios.

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.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNo
urlNo
nameNo
issuesNo
Behavior2/5

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

Description adds no behavioral context beyond annotations. Annotations indicate readOnly=false, but no details on permissions, idempotency, or side effects. Description does not disclose any traits.

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?

Single sentence, efficiently front-loaded with verb and resource. However, could be slightly more informative given tool complexity, but still concise.

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?

Given 13 parameters and availability of output schema, description covers only basic purpose. Lacks context on return value or action outcome, but output schema presumably covers return. Adequate but minimal.

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 has 100% coverage, so baseline is 3. Description does not add semantic information for parameters beyond what schema already provides.

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?

Description uses specific verb 'Create' and resource 'test case' with location 'Allure TestOps'. It clearly distinguishes from sibling tools for other operations (e.g., update, delete) and other entities (e.g., defects, test suites).

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?

No guidance on when to use this tool vs alternatives. Does not mention prerequisites, context, or exclusions despite many sibling tools.

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