Skip to main content
Glama

Get Test Case Details

get_test_case_details
Read-onlyIdempotent

Retrieve complete details of a test case, including steps, tags, custom fields, and attachments, to understand its current state before making updates.

Instructions

Get complete details of a specific test case.

Retrieves all information about a test case including its steps, tags, custom fields, and attachments. For each attachment, call prepare_attachment_download with its attachment_id, attachment_kind, and test_case_id, then HTTP GET the returned Lucius URL. Use this before updating a test case to understand its current state.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idNoAllure TestOps project ID to list test cases from.
test_case_idYesID of the test case to retrieve.
output_formatNoOutput format: 'json' (default) or 'plain'.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNo
urlNo
nameNo
tagsNo
stepsNo
statusNo
attachmentsNo
descriptionNo
preconditionNo
custom_fieldsNo

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed3 schema fields changedv0.15.0
    • removedOutput schema / $defs / Attachment
      Removed value: -{
      -  "additionalProperties": false,
      -  "description": "A lightweight attachment reference.",
      -  "properties": {
      -    "id": {
      -      "anyOf": [
      -        {
      -          "type": "string"
      -        },
      -        {
      -          "type": "null"
      -        }
      -      ],
      -      "default": null,
      -      "description": "Attachment identifier.",
      -      "title": "Id"
      -    },
      -    "name": {
      -      "description": "Attachment filename or display name.",
      -      "title": "Name",
      -      "type": "string"
      -    }
      -  },
      -  "required": [
      -    "name"
      -  ],
      -  "title": "Attachment",
      -  "type": "object"
      -}
    • addedOutput schema / $defs / TestCaseAttachmentOutput
      Added value: +{
      +  "additionalProperties": false,
      +  "description": "A test-case attachment reference safe to pass to the preparation tool.",
      +  "properties": {
      +    "attachment_id": {
      +      "anyOf": [
      +        {
      +          "minimum": 1,
      +          "type": "integer"
      +        },
      +        {
      +          "type": "null"
      +        }
      +      ],
      +      "default": null,
      +      "description": "Attachment identifier for preparation.",
      +      "title": "Attachment Id"
      +    },
      +    "attachment_kind": {
      +      "const": "test_case",
      +      "default": "test_case",
      +      "description": "Verified attachment owner kind for prepare_attachment_download.",
      +      "title": "Attachment Kind",
      +      "type": "string"
      +    },
      +    "content_length": {
      +      "anyOf": [
      +        {
      +          "minimum": 0,
      +          "type": "integer"
      +        },
      +        {
      +          "type": "null"
      +        }
      +      ],
      +      "default": null,
      +      "description": "Attachment byte length when available.",
      +      "title": "Content Length"
      +    },
      +    "content_type": {
      +      "anyOf": [
      +        {
      +          "type": "string"
      +        },
      +        {
      +          "type": "null"
      +        }
      +      ],
      +      "default": null,
      +      "description": "Attachment MIME type when available.",
      +      "title": "Content Type"
      +    },
      +    "name": {
      +      "description": "Attachment filename or display name.",
      +      "title": "Name",
      +      "type": "string"
      +    },
      +    "test_case_id": {
      +      "anyOf": [
      +        {
      +          "minimum": 1,
      +          "type": "integer"
      +        },
      +        {
      +          "type": "null"
      +        }
      +      ],
      +      "default": null,
      +      "description": "Required owner context for preparation.",
      +      "title": "Test Case Id"
      +    }
      +  },
      +  "required": [
      +    "name"
      +  ],
      +  "title": "TestCaseAttachmentOutput",
      +  "type": "object"
      +}
    • changedOutput schema / properties / attachments / anyOf
      Previous value: -[
      -  {
      -    "items": {
      -      "$ref": "#/$defs/Attachment"
      -    },
      -    "type": "array"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "items": {
      +      "$ref": "#/$defs/TestCaseAttachmentOutput"
      +    },
      +    "type": "array"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
  2. Changed1 schema field changedv0.14.0
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "$defs": {
      +    "Attachment": {
      +      "additionalProperties": false,
      +      "description": "A lightweight attachment reference.",
      +      "properties": {
      +        "id": {
      +          "anyOf": [
      +            {
      +              "type": "string"
      +            },
      +            {
      +              "type": "null"
      +            }
      +          ],
      +          "default": null,
      +          "description": "Attachment identifier.",
      +          "title": "Id"
      +        },
      +        "name": {
      +          "description": "Attachment filename or display name.",
      +          "title": "Name",
      +          "type": "string"
      +        }
      +      },
      +      "required": [
      +        "name"
      +      ],
      +      "title": "Attachment",
      +      "type": "object"
      +    },
      +    "CustomFieldEntry": {
      +      "additionalProperties": false,
      +      "description": "A named custom-field value exposed by test-case details.",
      +      "properties": {
      +        "name": {
      +          "description": "Custom field name.",
      +          "title": "Name",
      +          "type": "string"
      +        },
      +        "value": {
      +          "description": "Rendered custom field value.",
      +          "title": "Value",
      +          "type": "string"
      +        }
      +      },
      +      "required": [
      +        "name",
      +        "value"
      +      ],
      +      "title": "CustomFieldEntry",
      +      "type": "object"
      +    },
      +    "Step": {
      +      "additionalProperties": false,
      +      "description": "A serialized scenario step, including recursive shared-step children.",
      +      "properties": {
      +        "action": {
      +          "anyOf": [
      +            {
      +              "type": "string"
      +            },
      +            {
      +              "type": "null"
      +            }
      +          ],
      +          "default": null,
      +          "description": "Inline step action.",
      +          "title": "Action"
      +        },
      +        "expected": {
      +          "anyOf": [
      +            {
      +              "type": "string"
      +            },
      +            {
      +              "type": "null"
      +            }
      +          ],
      +          "default": null,
      +          "description": "Expected result for an inline step.",
      +          "title": "Expected"
      +        },
      +        "index": {
      +          "description": "One-based step index.",
      +          "minimum": 1,
      +          "title": "Index",
      +          "type": "integer"
      +        },
      +        "shared_step_id": {
      +          "anyOf": [
      +            {
      +              "type": "integer"
      +            },
      +            {
      +              "type": "null"
      +            }
      +          ],
      +          "default": null,
      +          "description": "Referenced shared-step identifier.",
      +          "title": "Shared Step Id"
      +        },
      +        "shared_step_url": {
      +          "anyOf": [
      +            {
      +              "type": "string"
      +            },
      +            {
      +              "type": "null"
      +            }
      +          ],
      +          "default": null,
      +          "description": "Referenced shared-step URL.",
      +          "title": "Shared Step Url"
      +        },
      +        "steps": {
      +          "anyOf": [
      +            {
      +              "items": {
      +                "$ref": "#/$defs/Step"
      +              },
      +              "type": "array"
      +            },
      +            {
      +              "type": "null"
      +            }
      +          ],
      +          "default": null,
      +          "description": "Nested shared-step children.",
      +          "title": "Steps"
      +        },
      +        "type": {
      +          "anyOf": [
      +            {
      +              "type": "string"
      +            },
      +            {
      +              "type": "null"
      +            }
      +          ],
      +          "default": null,
      +          "description": "Step kind, such as shared_step.",
      +          "title": "Type"
      +        }
      +      },
      +      "required": [
      +        "index"
      +      ],
      +      "title": "Step",
      +      "type": "object"
      +    }
      +  },
      +  "additionalProperties": false,
      +  "description": "Structured details for one test case.",
      +  "properties": {
      +    "attachments": {
      +      "anyOf": [
      +        {
      +          "items": {
      +            "$ref": "#/$defs/Attachment"
      +          },
      +          "type": "array"
      +        },
      +        {
      +          "type": "null"
      +        }
      +      ],
      +      "default": null,
      +      "title": "Attachments"
      +    },
      +    "custom_fields": {
      +      "anyOf": [
      +        {
      +          "items": {
      +            "$ref": "#/$defs/CustomFieldEntry"
      +          },
      +          "type": "array"
      +        },
      +        {
      +          "type": "null"
      +        }
      +      ],
      +      "default": null,
      +      "title": "Custom Fields"
      +    },
      +    "description": {
      +      "anyOf": [
      +        {
      +          "type": "string"
      +        },
      +        {
      +          "type": "null"
      +        }
      +      ],
      +      "default": null,
      +      "title": "Description"
      +    },
      +    "id": {
      +      "anyOf": [
      +        {
      +          "type": "integer"
      +        },
      +        {
      +          "type": "null"
      +        }
      +      ],
      +      "default": null,
      +      "title": "Id"
      +    },
      +    "name": {
      +      "anyOf": [
      +        {
      +          "type": "string"
      +        },
      +        {
      +          "type": "null"
      +        }
      +      ],
      +      "default": null,
      +      "title": "Name"
      +    },
      +    "precondition": {
      +      "anyOf": [
      +        {
      +          "type": "string"
      +        },
      +        {
      +          "type": "null"
      +        }
      +      ],
      +      "default": null,
      +      "title": "Precondition"
      +    },
      +    "status": {
      +      "anyOf": [
      +        {
      +          "type": "string"
      +        },
      +        {
      +          "type": "null"
      +        }
      +      ],
      +      "default": null,
      +      "title": "Status"
      +    },
      +    "steps": {
      +      "anyOf": [
      +        {
      +          "items": {
      +            "$ref": "#/$defs/Step"
      +          },
      +          "type": "array"
      +        },
      +        {
      +          "type": "null"
      +        }
      +      ],
      +      "default": null,
      +      "title": "Steps"
      +    },
      +    "tags": {
      +      "anyOf": [
      +        {
      +          "items": {
      +            "type": "string"
      +          },
      +          "type": "array"
      +        },
      +        {
      +          "type": "null"
      +        }
      +      ],
      +      "default": null,
      +      "title": "Tags"
      +    },
      +    "url": {
      +      "anyOf": [
      +        {
      +          "type": "string"
      +        },
      +        {
      +          "type": "null"
      +        }
      +      ],
      +      "default": null,
      +      "title": "Url"
      +    }
      +  },
      +  "title": "TestCaseDetailsOutput",
      +  "type": "object"
      +}
  3. First observedv0.11.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already cover the read-only, idempotent, and non-destructive nature. The description adds valuable behavioral context beyond annotations: attachments are not directly returned but require a separate prepare_attachment_download call followed by an HTTP GET to a Lucius URL. This is important for correct usage.

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?

The description is concise and front-loaded with the core purpose. The attachment workflow sentence earns its place. The opening sentence is slightly redundant with the title, but overall the structure is clear and 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?

With an output schema present, full parameter schema coverage, and annotations describing the safety profile, the description covers the essential behavior, attachment handling workflow, and a relevant use case. Nothing critical is missing for an agent to invoke this tool correctly.

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 description coverage is 100%, so the schema already documents all three parameters. The description does not add much parameter-level detail beyond clarifying that test_case_id is also needed in the attachment download workflow. This meets the baseline but does not exceed it.

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 retrieves complete details of a specific test case, listing the included components (steps, tags, custom fields, attachments). This distinguishes it from sibling tools like list_test_cases, get_test_case_custom_fields, and prepare_attachment_download.

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?

The description explicitly says to use this before updating a test case to understand its current state, and it gives a concrete follow-up workflow for downloading attachments. It provides clear context but does not explicitly state when not to use it or compare it to alternatives.

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

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/ivanostanin/lucius-mcp'

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