Skip to main content
Glama
Sign In
TestOps MCP Server

TestOps MCP Server

by kirchik95
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get-test-case-scenario

Retrieve the scenario steps of a test case, including Gherkin Given/When/Then and manual steps, to review test coverage.

Instructions

Get the scenario (steps) of a test case. Reads both Gherkin scenarios (Given/When/Then) and manual steps added through the UI.

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": {
      "id": "<id>"
    },
    "name": "get-test-case-scenario"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesTest case ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.7.0

TDQS

A4.3/5.0
Behavior4/5

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

Since no annotations provided, description carries full burden. It states it is a read operation ('reads') and specifies the content (Gherkin and manual steps). No behavioral traits beyond reading are disclosed, which is acceptable for a simple getter.

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?

Single sentence that front-loads the purpose. No unnecessary words. Every part earns 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?

Simple tool with one parameter, no output schema. Description fully covers what the tool does and what it returns. No missing information for its complexity level.

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% (parameter 'id' described as 'Test case ID'). Description adds no extra meaning beyond schema. Baseline 3 is appropriate; no added value but schema already sufficient.

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 the verb 'get', the resource 'scenario (steps) of a test case', and distinguishes from siblings by specifying it reads both Gherkin scenarios and manual steps. It differentiates from tools like get-test-case that might retrieve the entire test case.

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?

Description implies when to use (to retrieve test case steps) but does not explicitly state when not to use or mention alternatives like get-test-case or get-test-case-overview. Context is clear but lacks exclusion guidance.

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

Deploy Server

Other Tools