testit-mcp-server

upload_test_result_attachment

Attach a screenshot or log file to a test result by submitting the result ID, filename, MIME type, and base64 content; returns the new attachment ID.

Instructions

Attach a file (screenshot, log) to a test result. Returns the new attachment id.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "id": "<id>",
      "filename": "<filename>",
      "contentType": "<contentType>",
      "contentBase64": "<contentBase64>"
    },
    "name": "upload_test_result_attachment"
  }
}

Input Schema

Name	Required	Description
`id`	Yes	Test result UUID.
`filename`	Yes	File name including extension.
`contentType`	Yes	MIME type, e.g. image/png.
`contentBase64`	Yes	File content encoded as base64.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0Nov 14, 2026

TDQS

B3.3/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=false, openWorldHint=true, idempotentHint=false, and destructiveHint=false, so the write/non-destructive profile is covered. The description adds that it returns the new attachment id, which is genuinely useful since there is no output schema, but omits any file-size, content-type, or repeated-upload behavior (important given idempotentHint=false).

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?

Two short sentences, zero filler, with the action stated first and the return value second. Nothing could be removed without losing information.

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?

For a simple single-file upload this covers the essentials and discloses the return value despite no output schema. However, an open-world, non-idempotent upload with a base64 payload would benefit from at least noting size/type constraints and whether repeat uploads create duplicates, which are absent.

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 coverage is 100%, and each parameter already carries a description (UUID, filename with extension, MIME type, base64 content). The description adds no syntax or format meaning beyond what the schema states, so the baseline 3 applies.

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

Purpose4/5

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

States a specific verb (attach) and resource (file to a test result), with concrete examples of file kinds (screenshot, log). This distinguishes it from the broader upload_attachment sibling by naming the target 'test result', though it doesn't call out the distinction explicitly.

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?

The description says what it does but gives no guidance on when to pick this over upload_attachment, upload_work_item_attachment, or upload_attachment-like siblings, and no prerequisites (e.g., test result must exist, size limits). Usage is only implied by the tool's purpose.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server