Skip to main content
Glama

create_case

Create a new test case in QASE test management platform to document and organize testing procedures for software quality assurance.

Instructions

Create a new test case

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
codeYes
testCaseYes

Implementation Reference

  • The MCP tool handler for 'create_case' which parses input arguments using CreateCaseSchema and delegates to the createCase helper function.
    .with({ name: 'create_case' }, ({ arguments: args }) => {
      const { code, testCase } = CreateCaseSchema.parse(args);
      return createCase(code, testCase);
    })
  • Zod schema for validating input to the create_case tool: project code and test case data.
    export const CreateCaseSchema = z.object({
      code: z.string(),
      testCase: z.record(z.any()).transform((v) => v as TestCaseCreate),
    });
  • src/index.ts:180-184 (registration)
    Registration of the 'create_case' tool in the MCP server's ListToolsRequestSchema handler, including name, description, and input schema.
    {
      name: 'create_case',
      description: 'Create a new test case',
      inputSchema: zodToJsonSchema(CreateCaseSchema),
    },
  • The core createCase function that pipes the Qase client createCase method through toResult for result handling.
    export const createCase = pipe(
      client.cases.createCase.bind(client.cases),
      toResult,
    );
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. 'Create' implies a write/mutation operation, but the description doesn't disclose permissions needed, whether creation is idempotent, error handling, or what happens on success (e.g., returns a case ID). It lacks critical behavioral context for a creation tool.

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?

The description is extremely concise with a single sentence, 'Create a new test case', which is front-loaded and wastes no words. It efficiently states the core action, though this brevity contributes to gaps in other dimensions.

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?

Given the tool's complexity (a creation operation with 2 parameters, including a nested object), no annotations, and no output schema, the description is incomplete. It doesn't explain what 'code' and 'testCase' represent, what the tool returns, or any behavioral traits, making it inadequate for safe and effective use.

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

Parameters2/5

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

Schema description coverage is 0%, so the schema provides no parameter descriptions. The tool description doesn't mention any parameters, failing to compensate for the coverage gap. Parameters 'code' and 'testCase' (a nested object) are entirely undocumented, leaving their purpose and format ambiguous.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Create a new test case' clearly states the verb ('Create') and resource ('test case'), but it's vague about what a 'test case' entails in this context. It distinguishes from siblings like 'create_plan' or 'create_suite' by specifying the resource type, but lacks specificity about the domain or system involved.

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 is provided on when to use this tool versus alternatives like 'update_case' or 'get_case'. The description doesn't mention prerequisites, context, or exclusions, leaving the agent to infer usage from the tool name alone.

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/rikuson/mcp-qase'

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