Skip to main content
Glama

Get Test Case

get_test_case

Retrieve a test case from QA Sphere by its marker (e.g., BDI-123) to access test details for development workflows.

Instructions

Get a test case from QA Sphere using a marker in the format PROJECT_CODE-SEQUENCE (e.g., BDI-123). You can use URLs like: https://acme-corp.eu2.qasphere.com/project/%PROJECT_CODE%/tcase/%SEQUENCE%?any Extract %PROJECT_CODE% and %SEQUENCE% from the URL and use them as the marker.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
markerYesTest case marker in format PROJECT_CODE-TEST_CASE_SEQUENCE (e.g., BDI-123)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesUnique identifier of the test case
posYesOrdered position (0-based) of the test case in its folder
seqYesSequence number of the test case within its project (assigned incrementally)
tagsNoList of test case tags
typeYesType of the test case. Known values: "standalone" | "template" | "filled"
filesYesList of files attached to the test case
linksYesAdditional links relevant to the test case
stepsNoList of test case steps
titleYesTitle of the test case
commentYesTest case precondition text (HTML). DEPRECATED — prefer the `precondition` object
isDraftYesWhether the test case is still in draft state
isEmptyYesWhether the test case is empty (has no precondition and steps)
versionYesVersion of the test case. Updates (except folder/pos) create a new version
authorIdYesUnique identifier of the user who added the test case
folderIdYesIdentifier of the folder where the test case is placed
legacyIdYesLegacy identifier of the test case (empty string if none is set)
priorityYesPriority of the test case. Known values: "high" | "medium" | "low"
createdAtYesTest case creation time (ISO 8601)
updatedAtYesTest case last-update time (ISO 8601)
customFieldsNoCustom field values
preconditionNoTest case precondition object (may be a shared or standalone precondition)
requirementsNoTest case requirements
isLatestVersionYesWhether this is the latest version of the test case
numFilledTCasesNoNumber of corresponding filled test cases (only for template test cases)
parameterValuesNoParameter substitutions for filled test cases (only for template test cases)
templateTCaseIdNoCorresponding template test case ID (only for filled test cases)
filledTCaseTitleSuffixParamsNoParameter names whose substituted values are appended to each filled test case title for disambiguation (only for template test cases).
Behavior4/5

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

No annotations provided, so description bears full burden. Clearly a read operation (Get), no side effects implied. Does not mention authentication or rate limits, but for a simple get tool this is acceptable. The output schema exists, so return behavior is documented externally.

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 concise sentences. First states purpose, second provides critical usage nuance (URL conversion). No wasted words; every sentence earned its place.

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?

Given simple tool (1 param, output schema present), description fully covers how to identify the test case. No gaps – the agent has all needed info to invoke correctly.

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?

Single parameter (marker) with schema coverage 100%. Description adds significant value beyond schema by explaining the format and providing a real-world URL extraction example, making it easy for the agent to construct the parameter correctly.

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 'Get a test case' with specific resource (test case) and verb (get). Distinguishes from siblings like create/update/list_test_cases by focusing on retrieval by marker. Includes the exact marker format and URL extraction, leaving no ambiguity.

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

Usage Guidelines4/5

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

Describes how to use (via marker or URL), implicitly indicating when to use (when you have a marker) vs. alternatives for listing/searching. Lacks explicit exclusion statements but the specific retrieval context is clear.

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/Hypersequent/qasphere-mcp'

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