Skip to main content
Glama

Get Manual Test Case

get_manual_test_case
Read-only

Retrieve a manual test case's full details, including steps, preconditions, postconditions, metadata, linked issues, comments, version history, and run results, to review current state before updating.

Instructions

Get the full details of one manual test case: steps, preconditions, postconditions, metadata, linkedIssues, and activity (comments, version history, and execution results across all manual runs). caseId accepts either the internal _id or a human-readable ID like "TC-123". Call this before update_manual_test_case to see current steps, comments, and linked issues before modifying them. Version history and results are read-only — they reflect what happened, you cannot mutate them. Comments and linked issues are added via update_manual_test_case.

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": {
      "projectId": "<projectId>",
      "caseId": "<caseId>"
    },
    "name": "get_manual_test_case"
  }
}

Input Schema

NameRequiredDescriptionDefault
caseIdYesInternal _id or "TC-123" style ID
projectIdYesProject ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv2.2.0
    • addedInput schema / $schema
      Added value: +"http://json-schema.org/draft-07/schema#"
    • addedInput schema / additionalProperties
      Added value: +false
    • changedInput schema / properties / caseId / description
      Previous value: -"Test case ID (Required). Can be internal _id or human-readable ID like 'TC-123'."New value: +"Internal _id or \"TC-123\" style ID"
    • changedInput schema / properties / projectId / description
      Previous value: -"Project ID (Required). The TestDino project identifier."New value: +"Project ID"
  2. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered; the description adds value by disclosing that version history and execution results are immutable historical records and that activity spans all manual runs. It does not discuss cost, pagination, or size of the activity payload, keeping it short of a 5.

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?

Purpose and returned fields are front-loaded in the first sentence, with usage guidance, read-only caveats, and mutation routing following in order. Only mild redundancy remains, namely re-explaining the caseId formats already present in the schema.

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?

With no output schema, the description carries the burden of describing the return payload, and it does so by naming the major sections and the activity sub-streams. What is missing is granularity on shape or volume of the activity data, though that is a modest gap for a read-only fetch.

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 the schema already defines caseId as 'Internal _id or "TC-123" style ID', so the description's restatement of that dual-ID acceptance adds no meaning beyond structured data. projectId receives no elaboration at all. This is the baseline case where the schema does the work.

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?

States a specific verb and resource ('Get the full details of one manual test case') and enumerates the scope of what is returned: steps, preconditions, postconditions, metadata, linkedIssues, and activity. The singular 'one test case' plus the required caseId separates it from list_manual_test_cases without needing to name it.

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 says to call this before update_manual_test_case to view current steps, comments, and linked issues before modifying them, and adds a when-not: comments and linked issues are added via update_manual_test_case, not here. Both the recommended call order and the mutation routing are stated outright.

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