zephyr-squad-server-mcp

get_defect_statistics

Retrieve execution, requirement, and test statistics for one or more defects to analyze defect density and closure rates.

Instructions

Get execution/requirement/test statistics for one or more defects.

defects is a Jira key/id or a comma-separated string / list of them. Returns per-defect rollups (execution status totals, requirement & test counts) — useful for defect-density and closure-rate narratives.

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": {
      "defects": "<defects>"
    },
    "name": "get_defect_statistics"
  }
}

Input Schema

Name	Required	Description	Default
`defects`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jun 24, 2026

TDQS

A4/5.0

Behavior3/5

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

Describes return value and input format, but with no annotations, it doesn't explicitly state read-only nature or other behavioral traits.

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?

Very concise, three sentences, front-loaded with main purpose, no redundancy.

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?

Covers input and output adequately for a single-parameter tool without output schema, though could specify exact return field names.

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?

Adds value beyond schema by explaining defects parameter as Jira key/id and acceptable formats (comma-separated string or list), compensating for 0% schema coverage.

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?

Explicitly states it gets statistics for defects, listing types (execution, requirement, test) and mentioning per-defect rollups, distinguishing from siblings like get_executions_by_defect.

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

Usage Guidelines3/5

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

Provides context of use (defect-density and closure-rate narratives) but does not explicitly compare to or exclude alternatives.

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