Skip to main content
Glama

Fetch recent test executions

wopee_fetch_recent_executions
Read-onlyIdempotent

Retrieve recent test case executions for the current project and their verdicts or execution status to check recently dispatched tests without suite UUIDs.

Instructions

Fetch the most recent test case executions for the current project (up to 20, newest first). Use this to check the status of recently dispatched tests without needing to remember specific suite UUIDs. Returns each run's verdict (PASSED, FAILED, or INCOMPLETE — the run never established a result, e.g. an infrastructure error, and says nothing about the application) or, for a run with no verdict yet, its execution status (IN_QUEUE, IN_PROGRESS, FINISHED, FAILED, STOPPED), plus agent reports. Takes no input; uses WOPEE_PROJECT_UUID from environment. Prefer this tool when the user asks 'what's the status?' or 'how did the tests go?' and you don't have the specific suite UUID handy.

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_recent_executions"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.26.3

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the description's job is added context, and it delivers: the 20-item cap, newest-first ordering, and the environment dependency WOPEE_PROJECT_UUID. It also decodes return semantics in advance—distinguishing a PASSED/FAILED/INCOMPLETE verdict, explaining that INCOMPLETE means the run never established a result and says nothing about the application, and listing execution statuses for runs without a verdict. It leaves 'agent reports' unexplained and says nothing about truncation behavior when more than 20 runs exist.

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?

Purpose, limit, and ordering are front-loaded, then return semantics, then the usage rule—a sensible information order. The verdict parenthetical is long but each clause carries real meaning (INCOMPLETE's meaning is genuinely non-obvious). Slightly dense prose with nested parentheses costs it a point on readability.

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?

With no output schema, the description carries the return-value burden and does so well for verdict and status fields, which is the core of the tool. What is missing is the shape of 'agent reports' and any indication of what happens when more than 20 runs exist (silent truncation vs pagination), which matters for an agent reporting completeness of results.

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?

There are zero parameters, so the baseline is 4. The description usefully discloses the implicit configuration that replaces parameters—project scoping comes from WOPEE_PROJECT_UUID in the environment and the call 'Takes no input'—which prevents an agent from hunting for a project argument. Nothing further about parameter semantics is possible for this tool.

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?

States a specific verb and resource ('Fetch the most recent test case executions'), plus scope ('for the current project'), ordering ('newest first') and a cap ('up to 20'). This is distinguishable from siblings that require suite UUIDs, so an agent can tell what it returns without opening anything else.

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?

Gives an explicit selection rule: use it when you don't have the specific suite UUID handy, and 'Prefer this tool when the user asks "what's the status?" or "how did the tests go?"'. That is a clear when-to-use condition tied to a concrete user phrasing. It stops short of naming the alternative tool or stating when NOT to use it (e.g. when a suite UUID is known), which keeps it at 4.

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