Skip to main content
Glama

Fetch test inventory (counts + statuses)

wopee_fetch_test_inventory
Read-onlyIdempotent

Retrieve every test case with its current execution status, including never-run tests marked NOT_RUN, optionally scoped to one analysis. Use it for total counts and complete test lists.

Instructions

The authoritative tool for how many tests exist and their latest status. Returns, per analysis, the FULL list of authored test cases joined with their latest execution status — including never-run ones as NOT_RUN. Use this for questions like 'how many tests do I have', 'list the scenarios/test cases in A001', or 'show executed and not-run tests in one table'. Terminology: a 'scenario' is a test case; test cases are grouped under user stories (US001) and identified as US001:TC001. Reusable blocks (user story R001) are counted separately (reusableBlockCount) and are building blocks, not runnable, so they never carry an execution status. Regular tests are all non-R001 test cases. Read-only. Takes an optional analysisIdentifier (e.g. A001) to scope to one analysis; omit to cover every analysis in the project. Prefer this over wopee_fetch_recent_executions / wopee_fetch_executed_test_cases when the user asks about totals or the complete list — those return only test cases that have already run. Each test case carries executedTestCaseUuid (the latest run's uuid, the same one wopee_dispatch_agent returns) and verdictGateDisagreed (true when a verdict gate disagreed with a PASSED verdict — report it alongside the pass). Status UNKNOWN means the execution history could not be read (the reason is in the analysis's executionHistoryError); do not report such tests as not run.

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": "wopee_fetch_test_inventory"
  }
}

Input Schema

NameRequiredDescriptionDefault
analysisIdentifierNoOptional analysis identifier (e.g. A001) to scope the inventory to a single analysis. Omit to include every analysis in the project.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.32.1
    • removedInput schema / additionalProperties
      Removed value: -false
  2. Addedv1.29.1

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare read-only/idempotent, and the description goes well beyond them: never-run cases appear as NOT_RUN, UNKNOWN means execution history was unreadable with the reason in executionHistoryError, and it warns not to misreport those as not-run. It also explains reusableBlockCount scope (R001 blocks are non-runnable and never carry status) and surfaces verdictGateDisagreed as a flag to report alongside a PASSED verdict.

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?

It is front-loaded with the purpose and disambiguation before the terminology and edge-case detail, and nearly every sentence carries decision-relevant information. It is dense for one paragraph, with minor overlap between the terminology sentence and the reusable-block sentence, but nothing is truly wasteful.

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?

There is no output schema, so the description carries the return-shape burden and does so fully — per-analysis grouping, full test case list, status values, executedTestCaseUuid linkage, and the reusable-block count. An agent has everything needed to call it correctly and to report results accurately.

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% and the single parameter is already fully documented there, including the omit-to-cover-everything behavior. The description restates the same A001 scoping with the same semantics, adding little beyond the schema, so the baseline 3 applies.

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 states a specific verb and resource up front — 'The authoritative tool for how many tests exist and their latest status' — and explains exactly what the response contains (authored test cases joined with latest execution status). It also distinguishes itself linguistically from the executed-only siblings, so an agent can pick it without opening a schema.

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

Usage Guidelines5/5

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

It gives concrete trigger phrases ('how many tests do I have', 'list the scenarios/test cases in A001'), an explicit exclusion rule ('Prefer this over wopee_fetch_recent_executions / wopee_fetch_executed_test_cases when the user asks about totals or the complete list'), and states the condition those alternatives cover (only already-run cases). It also says when to pass versus omit the analysis identifier.

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