TestMu AI Test Manager MCP

Get Test Manager Test Case Instance by ID

tm.get_testCaseInstanceById

Fetch detailed information for a specific test case instance by its instance ID, including result, timing, environment, and step-level results. Use to inspect instance details without modifying data.

Instructions

Retrieves full detail for ONE specific test case instance, identified by its own numeric test_instance_id (NOT the same as test_case_id - get it from tm.get_testCaseInstancesByTestRunId's 'Instance ID' field). TERMINOLOGY: a 'test case instance' is ONE (test case x environment) pairing within a run, not one test case - if a test case is assigned 2 environments in the same run, each environment has its own separate instance ID and its own separate result here. Includes the instance's own result (Passed/Failed/Skipped/Not Started), timing, remarks, environment, and per-step results (each step's own status/outcome/remarks, plus its own Step ID for use with tm.update_testCaseInstanceStep) - detail that tm.get_testCaseInstancesByTestRunId doesn't expose. Setting/inspecting this instance's result only affects its standing within this run - it does NOT change the underlying test case's own stored status in Test Manager. Read-only; does not modify anything.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "tm.get_testCaseInstanceById"
  }
}

Input Schema

Name	Required	Description	Default
`test_instance_id`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 10, 2026

TDQS

A4.5/5.0

Behavior5/5

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

No annotations provided, so description fully handles behavioral disclosure. States read-only, does not modify, explains effect scope (run-level only, not underlying test case status), and lists included fields (result, timing, remarks, environment, per-step results).

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 somewhat long but each sentence adds value. Front-loaded with purpose, then terminology clarification, then detail on output and behavior. Could be slightly more concise, but efficient for the complexity.

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?

Given no output schema, description provides adequate overview of returned data: instance result, timing, remarks, environment, per-step results with own status/outcome/remarks and step IDs. Lacks explicit mention of all possible fields, but sufficient for understanding.

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 0%, so description must explain parameter. It defines test_instance_id as numeric ID, distinguishes from test_case_id, and tells how to get it (from sibling tool's 'Instance ID' field). Adds value 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?

Description clearly states it retrieves full detail for one specific test case instance, clarifies terminology differentiating from test case, and contrasts with sibling tool tm.get_testCaseInstancesByTestRunId which lacks this detailed output.

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?

Explicitly says when to use (need full detail for one instance), contrasts with sibling tool, and states read-only nature. Could be improved by explicitly listing when not to use, but clear enough.

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

Deploy Server