Skip to main content
Glama

create_result

Record test execution outcomes in QASE test management by submitting results with case codes and identifiers.

Instructions

Create test run result

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
codeYes
idYes
resultYes

Implementation Reference

  • Core handler function that executes the creation of a test result by piping the Qase client's createResult method through the toResult utility.
    export const createResult = pipe(
      client.results.createResult.bind(client.results),
      toResult,
    );
  • Zod schema defining the input structure for the create_result tool: project code, test case/run ID, and result data.
    export const CreateResultSchema = z.object({
      code: z.string(),
      id: z.number(),
      result: z.record(z.any()).transform((v) => v as ResultCreate),
    });
  • src/index.ts:156-158 (registration)
    Tool registration in the list of available tools returned by ListToolsRequestHandler.
    name: 'create_result',
    description: 'Create test run result',
    inputSchema: zodToJsonSchema(CreateResultSchema),
  • Dispatch handler in CallToolRequestHandler that validates arguments with the schema and invokes the createResult function.
    .with({ name: 'create_result' }, ({ arguments: args }) => {
      const { code, id, result } = CreateResultSchema.parse(args);
      return createResult(code, id, result);
    })
Behavior1/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. The description only states the action ('Create') without any details on permissions, side effects, response format, error handling, or rate limits. For a mutation tool with zero annotation coverage, this is a critical gap in transparency.

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 extremely concise with a single phrase, 'Create test run result', which is front-loaded and wastes no words. However, this brevity comes at the cost of under-specification, as it lacks necessary details for effective tool use.

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

Completeness1/5

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

Given the complexity (mutation tool with 3 parameters, nested objects, no output schema, and 0% schema coverage), the description is severely incomplete. It does not explain what the tool returns, how parameters interact, or behavioral aspects, making it inadequate for the agent to use the tool correctly without additional context.

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

Parameters1/5

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

Schema description coverage is 0%, meaning none of the three parameters (code, id, result) are documented in the schema. The description does not add any meaning or explanation for these parameters, failing to compensate for the lack of schema documentation. This leaves the agent guessing about parameter purposes and formats.

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

Purpose2/5

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

The description 'Create test run result' is essentially a tautology of the tool name 'create_result'. While it indicates the action (create) and resource (test run result), it doesn't specify what constitutes a 'test run result' or how this differs from sibling tools like 'create_result_bulk' or 'update_result'. The purpose is stated but lacks differentiation and specificity.

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

Usage Guidelines1/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. The description does not mention prerequisites, context, or comparisons to sibling tools such as 'create_result_bulk' for bulk operations or 'update_result' for modifications. This leaves the agent without direction on appropriate usage scenarios.

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