Skip to main content
Glama
Sign In
Zephyr Scale MCP Server

Zephyr Scale MCP Server

by Milo0821
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_test_case

Retrieve comprehensive details of a test case by its key to understand its steps, status, and associated data.

Instructions

Get detailed information about a specific 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": {
      "test_case_key": "<test_case_key>"
    },
    "name": "get_test_case"
  }
}

Input Schema

NameRequiredDescriptionDefault
test_case_keyYesTest case key (e.g., PROJ-T123)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.7.0

TDQS

B3.1/5.0
Behavior2/5

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

No annotations exist, so the description must disclose behavioral traits. It only states 'Get', implying a read operation, but does not elaborate on permissions, rate limits, or side effects. The minimal verb choice provides very limited transparency.

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?

The description is a single, efficient sentence with no unnecessary words. It is front-loaded and effectively communicates the core action.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple read tool with one parameter and no output schema, the description is adequate but minimal. It does not mention return format or any additional context that would help an agent, though the tool is straightforward.

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% for the single parameter test_case_key, which already includes a clear description and example. The tool description adds no additional meaning beyond what the schema provides, so baseline score of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a clear verb 'Get' and specifies the resource 'specific test case', effectively conveying the tool's purpose. It distinguishes from sibling tools like create_test_case or delete_test_case. However, 'detailed information' is somewhat vague, lacking specificity about what details are returned.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives, nor any conditions or prerequisites. It is purely a statement of function without contextual advice.

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