Skip to main content
Glama
verifyax

VerifyAX MCP

Official
by verifyax
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

List recent runs

list_recent_runs
Read-only

Browse recent simulation runs in your VerifyAX workspace, optionally filtered by status, agent, scenario, date range, or run group. Returns run UUID, status, agent, scenario, and evaluation handle.

Instructions

Lists recent simulation runs in your VerifyAX workspace, optionally filtered by status, agent, scenario, date range, search text, or run group. Returns each run’s uuid, status, agent, scenario, and evaluation handle.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNo
offsetNo
searchNoFree-text search across run metadata.
statusNoFilter by run status. Known values: CREATED, IN_PROGRESS, COMPLETED, FAILED, CANCELLED (open enum — the API may add statuses, which are forwarded rather than rejected).
date_toNoISO 8601 end of the created-at window.
date_fromNoISO 8601 start of the created-at window.
agent_uuidNo
scenario_uuidNo
run_group_uuidNoFilter to runs in a linked run group.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.3.7
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / offset / maximum
      Added value: +9007199254740991
  2. First observedv1.0.0

TDQS

A3.8/5.0
Behavior3/5

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

readOnlyHint=true already declares the safety profile, so the description's main added value is naming the returned fields (uuid, status, agent, scenario, evaluation handle). It does not mention pagination behavior despite limit/offset, and adds no rate-limit or ordering context.

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?

Two tightly written sentences with no filler; the purpose is front-loaded and the filter list and return summary follow logically.

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 does the right thing by enumerating the returned fields. The only material gap is the absence of any pagination (limit/offset) or result-ordering note for what is clearly a paged listing tool.

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 56%, so roughly half the parameters carry no inline documentation. The description compensates by naming the filterable dimensions (status, agent, scenario, date range, search text, run group), matching the schema fields but adding no syntax or format detail beyond them.

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 (Lists) and resource (recent simulation runs) scoped to a workspace, and enumerates the available filter dimensions. An agent can distinguish this bulk-list tool from the singular get_run_details sibling without opening either schema.

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?

The word 'optionally filtered' implies this is a browse/query tool, but it never states when to reach for it versus get_run_details or how the filters combine. Usage is implied rather than directed.

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