Skip to main content
Glama
vilaabo

zephyr-scale-mcp

by vilaabo

create_test_result

Create a new execution record for a test case that is an item in a test run. Appends a result with status, duration, assignee, and custom fields.

Instructions

Create a NEW execution (test result) for a test case that is already an item of a test run (test cycle). Appends a new result to the item's execution history — to amend the latest result instead, use update_last_test_result. This tool CANNOT add a test case to a run: the run's item list is fixed when the run is created, and the call fails if the case is not among the run's items. Only the fields you pass are sent. Default statuses: 'Not Executed', 'In Progress', 'Pass', 'Fail', 'Blocked' — case-sensitive internal names; instances may define custom ones. Durations (executionTime) are in milliseconds; dates are ISO 8601. scriptResults record per-step outcomes for STEP_BY_STEP scripts as { index (0-based), status, comment? }. If the same test case is included in the run as several items, disambiguate with matchEnvironment / matchUserKey. Returns { id } of the created result.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
statusNoExecution status. Default statuses: 'Not Executed', 'In Progress', 'Pass', 'Fail', 'Blocked' — case-sensitive internal names; instances may define custom ones.
commentNoComment (HTML allowed)
versionNo
iterationNo
assignedToNoAssignee. Jira *user key* (e.g. 'JIRAUSER10000'), NOT a username or e-mail — resolve it with find_jira_user.
executedByNoExecutor. Jira *user key* (e.g. 'JIRAUSER10000'), NOT a username or e-mail — resolve it with find_jira_user.
issueLinksNoJira issue keys to link, e.g. ["PROJ-123"]
testRunKeyYesTest run (cycle) key, e.g. PROJ-R123
environmentNoEnvironment name as configured in the project (case-sensitive), e.g. "Chrome"
testCaseKeyYesTest case key, e.g. PROJ-T123 — must already be one of the run's items
customFieldsNoCustom field values keyed by field name
matchUserKeyNoRun-item selector, sent as the 'userKey' QUERY parameter (never in the body): when the same test case is included in the run as several items, targets the item by its executor's Jira user key (e.g. 'JIRAUSER10000').
actualEndDateNoISO 8601
executionTimeNoExecution duration in milliseconds
scriptResultsNoPer-step results (STEP_BY_STEP scripts)
actualStartDateNoISO 8601, e.g. 2026-07-20T14:00:00Z
matchEnvironmentNoRun-item selector, sent as the 'environment' QUERY parameter (never in the body): when the same test case is included in the run as several items, targets the item with this environment (case-sensitive). Distinct from the 'environment' body field, which sets the environment recorded on the result.
Behavior5/5

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

With no annotations, description fully discloses behavior: appends to history, sends only passed fields, default statuses, duration format, ISO 8601 dates, scriptResults structure, and that matchUserKey/matchEnvironment are query parameters. No contradictions.

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?

Despite length, every sentence earns its place. Front-loaded with core purpose and limitation. Structured logically: purpose, sibling distinction, constraints, default values, formats, edge-cases, return value. No fluff given the complexity (17 params).

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

Completeness5/5

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

Highly complete for a 17-param tool with no output schema. Covers required params, optional defaults, edge cases (disambiguation, custom statuses), parameter location (query vs body), and return format {id}. Nested scriptResults explained clearly.

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

Parameters5/5

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

Adds significant meaning beyond schema: explains that assignedTo/executedBy use Jira user keys (not usernames), distinguishes matchEnvironment/matchEnvironment query params from body field, clarifies duration/date formats, and elaborates on scriptResults structure. Schema coverage is 88% but description enriches understanding.

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?

Clearly states it creates a new test result execution, distinguishes from 'update_last_test_result', and explicitly explains what the tool cannot do (add a test case to a run). Verb+resource+scope are specific.

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

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides explicit when-to-use (create new result) and when-not (amend latest, use update_last_test_result). States pre-conditions (test case must be run item) and explains disambiguation via matchEnvironment/matchUserKey for duplicate items.

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/vilaabo/zephyr-scale-mcp'

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