Skip to main content
Glama
qase-tms

Qase MCP Server

Official
by qase-tms

qase_attachment_upload

Upload an attachment file to Qase and retrieve its hash for use in other Qase operations. Accepts base64 content or a local file path.

Instructions

Upload a file attachment and get back its hash, which the attachments field of qase_case_upsert, qase_result_record, qase_ci_report, qase_triage_defect, and qase_shared_step_upsert accepts. This is the only way to obtain such a hash — the upload endpoint needs multipart/form-data, which qase_api cannot send. Pass the file as base64 (file_base64), which is the only option when the server runs remotely, such as the hosted connector; file_path works only when the server runs on the same machine as the file.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
codeYesProject code (2-10 uppercase letters, numbers, or underscores)
fileNoDeprecated: prefer file_base64 or file_path, which say which one you mean. Accepts either an absolute path to an existing file or base64 content.
filenameYesOriginal filename with extension
file_pathNoAbsolute path to a file on the machine running THIS server. Only usable for a local stdio server; a remote server cannot see your filesystem — send file_base64 instead.
file_base64NoFile content, base64 encoded. Use this whenever the server is not on the same machine as the file — including the hosted connector, where it is the only option.
Behavior4/5

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

Annotations already indicate non-read-only and non-destructive behavior. The description adds valuable context: the need for multipart/form-data, the server-location constraints, and the return of a hash. This exceeds the baseline and enriches agent understanding without contradicting annotations.

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?

Three concise sentences, front-loaded with purpose and output. The second sentence explains the critical limitation ('only way'), and the third delivers actionable parameter guidance. No redundant phrases or irrelevant details.

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?

Despite no output schema, the description fully covers the return value (hash), dependent tools, and all parameter usage constraints. It provides sufficient context for an AI agent to use correctly on both local and remote servers.

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 100%, so baseline is 3. The description adds meaningful value beyond the schema: it deprecates the 'file' parameter in favor of explicit alternatives, and explains when to choose file_base64 vs file_path based on server location, which the schema descriptions do not fully convey.

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 clearly states the tool uploads a file attachment and returns a hash, and explicitly differentiates it from qase_api which cannot send multipart/form-data. It's specific about the verb, resource, and output.

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?

It explicitly states when to use this tool (to obtain a hash for attachment fields) and why qase_api is not an alternative (multipart/form-data limitation). It also provides conditional guidance on file_base64 vs file_path based on server locality, giving clear context for selection.

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

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