Skip to main content
Glama

get_manual_test_case

Retrieve detailed information of a manual test case, including steps, preconditions, custom fields, and inline activity such as comments, version history, execution results, and linked issues.

Instructions

Retrieve detailed information of a single manual test case, including steps, custom fields, preconditions, and all metadata. Activity is included inline: comments (latest), versions (latest 20 of the version history), results (latest 100 execution results across every manual run that ran this case), and linkedIssues (Jira tickets linked to the case). versions and results are READ-ONLY — they reflect what happened, you cannot mutate them. Use update_manual_test_case to add comments (updates.comments) or link issues (updates.issues).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
projectIdYesProject ID (Required). The TestDino project identifier.
caseIdYesTest case ID (Required). Can be internal _id or human-readable ID like 'TC-123'.

Implementation Reference

  • Main handler function that validates args, fetches API token, calls the API endpoint, and returns JSON content
    export async function handleGetManualTestCase(args?: GetManualTestCaseArgs) {
      // Read PAT from environment variable (set in mcp.json) or from args
      const token = getApiKey(args);
    
      if (!token) {
        throw new Error(
          "Missing TESTDINO_PAT environment variable. " +
            "Please configure it in your .cursor/mcp.json file under the 'env' section."
        );
      }
    
      // Validate required parameters
      if (!args?.projectId) {
        throw new Error("projectId is required");
      }
      if (!args?.caseId) {
        throw new Error("caseId is required");
      }
    
      try {
        const params = {
          projectId: String(args.projectId),
          caseId: String(args.caseId),
        };
    
        const getManualTestCaseUrl = endpoints.getManualTestCase(params);
    
        const response = await apiRequestJson<unknown>(getManualTestCaseUrl, {
          headers: {
            Authorization: `Bearer ${token}`,
          },
        });
    
        return {
          content: [
            {
              type: "text",
              text: JSON.stringify(response, null, 2),
            },
          ],
        };
      } catch (error) {
        const errorMessage = error instanceof Error ? error.message : String(error);
        throw new Error(`Failed to get manual test case details: ${errorMessage}`);
      }
    }
  • Tool definition with name, description, and input schema (projectId and caseId strings, both required)
    export const getManualTestCaseTool = {
      name: "get_manual_test_case",
      description:
        "Retrieve detailed information of a single manual test case, including steps, custom fields, preconditions, and all metadata. " +
        "Activity is included inline: `comments` (latest), `versions` (latest 20 of the version history), `results` (latest 100 execution results across every manual run that ran this case), and `linkedIssues` (Jira tickets linked to the case). " +
        "`versions` and `results` are READ-ONLY — they reflect what happened, you cannot mutate them. " +
        "Use update_manual_test_case to add comments (updates.comments) or link issues (updates.issues).",
      inputSchema: {
        type: "object",
        properties: {
          projectId: {
            type: "string",
            description: "Project ID (Required). The TestDino project identifier.",
          },
          caseId: {
            type: "string",
            description:
              "Test case ID (Required). Can be internal _id or human-readable ID like 'TC-123'.",
          },
        },
        required: ["projectId", "caseId"],
      },
    };
  • TypeScript interface defining the args shape for get_manual_test_case
    interface GetManualTestCaseArgs {
      projectId: string;
      caseId: string;
    }
  • src/index.ts:243-247 (registration)
    Registration routing: dispatches tool call requests to the handler when name matches 'get_manual_test_case'
    if (name === "get_manual_test_case") {
      return await handleGetManualTestCase(
        args as Parameters<typeof handleGetManualTestCase>[0]
      );
    }
  • src/index.ts:108-108 (registration)
    Tool is listed in the tools array passed to ListToolsRequestSchema handler, making it available to clients
    getManualTestCaseTool,
Behavior5/5

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

No annotations, so description fully handles transparency. Discloses that versions and results are read-only, and details the activity inline with limits (latest 20 versions, latest 100 results). Leaves no ambiguity about behavior.

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?

Description is slightly verbose but each sentence serves a purpose. Front-loaded with main purpose, then details activity. Could trim a few words but overall efficient.

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?

No output schema, but description thoroughly explains what is returned: steps, custom fields, preconditions, metadata, and activity with specifics. Covers parameters, limits, and behavior. Complete for its purpose.

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%, but description adds useful semantics: projectId is TestDino identifier, caseId accepts internal _id or human-readable ID like 'TC-123'. Adds clarity beyond schema.

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 it retrieves detailed info of a single manual test case, including steps, custom fields, preconditions, metadata, and activity. Distinguishes from update_manual_test_case and other get tools.

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?

Provides guidance to use update_manual_test_case for mutations. Implicitly clarifies that this is a read-only tool. Does not exhaustively list when to use over other get tools, but 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/testdino-hq/testdino-mcp'

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