Skip to main content
Glama
vilaabo

zephyr-scale-mcp

by vilaabo

update_last_test_result

Idempotent

Modify the last test result in a test run, updating only the fields you specify and leaving the rest unchanged.

Instructions

Update the LAST (most recent) test result of a run item. Partial update: ONLY the fields you pass are changed, everything else is preserved — do not send fields you do not want to modify. Older executions cannot be targeted; to record a new execution use create_test_result. The test case must already be one of the run's items (the run's composition is fixed at creation). 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 as { index (0-based), status, comment? }. If the same test case is included in the run as several items, disambiguate with matchEnvironment / matchUserKey.

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?

The description discloses key behaviors: partial update (only sent fields change), targeting only the latest result, requirement for run composition, and nuances like matchUserKey/matchEnvironment being query parameters. Annotations only provide idempotentHint, so the description carries the full behavioral burden and does so thoroughly.

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 front-loaded with the main purpose and structured logically. It covers all necessary details without being overly verbose, though a slightly tighter structure could improve conciseness.

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

Completeness4/5

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

Given the complexity (17 parameters, nested objects, query parameters), the description is largely complete. It covers update semantics, limitations, data types, and disambiguation. The lack of return value description is a minor gap, but the tool's context (update) makes the return somewhat predictable.

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

Parameters4/5

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

Schema coverage is high (88%), but the description adds value by explaining partial update semantics, duration units, date format, scriptResults structure, and special parameter behavior (e.g., query parameters vs body). This goes beyond schema descriptions.

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 specifies 'update the LAST (most recent) test result of a run item' with a clear verb and resource. It distinguishes from sibling 'create_test_result' by noting that older executions cannot be targeted. This provides precise purpose differentiation.

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?

Explicitly states when to use (update last result) and when not (use create_test_result for new execution). Also notes precondition that test case must already be a run item, and provides disambiguation hints for duplicate items. This is comprehensive guidance.

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