Regresco

Create flow

create_flow

Save a new persistent regression flow with all of its steps in one call (up to 100 steps, run in array order). Steps are validated before anything is saved; navigate and api URLs must be public. The flow stays in Regresco for scheduled and CI runs after this session.

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": {
      "projectId": "<projectId>",
      "name": "<name>",
      "steps": "<steps>"
    },
    "name": "create_flow"
  }
}

Input Schema

Name	Required	Description
`name`	Yes	Flow name, e.g. 'Login with email'
`steps`	Yes	Steps in the order they run
`device`	No	What the flow runs on. desktop: 1280x720. phone: 412x839 in Chromium, with a phone's touch and browser identity, so a site with no mobile version shows as it does there. Not a real device and not Safari. A flow on a phone can't have hover steps.
`projectId`	Yes	Project ID, as returned by Regresco tools
`description`	No	What the flow verifies

Output Schema

Name	Required	Description	Default
`flow`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 9, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already declare that this is a write operation (readOnlyHint=false) and not destructive. The description adds useful behavioral context beyond the annotations: steps are validated before anything is saved, navigate and api URLs must be public, the flow persists for scheduled and CI runs, and there is a 100-step limit.

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 three tight sentences with no filler. The most important scoping and behavioral details are front-loaded, and each sentence adds a distinct and useful piece of information.

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?

Given the tool's complexity, 100% schema description coverage, and the presence of an output schema, the description covers what an agent needs: creation semantics, validation order, URL constraints, persistence, and step limits. It does not need to repeat return-value details that the output schema supplies.

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%, so the schema already documents all parameters thoroughly. The description reinforces a few points such as the 100-step maximum, array execution order, and public URL constraint, but these are already present in the schema and it adds little new meaning about individual parameters.

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: 'Save a new persistent regression flow with all of its steps in one call.' It also clarifies the scope ('new', 'persistent', 'all of its steps') and distinguishes this from updating an existing flow by using 'new' and noting that the flow remains after the session.

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?

Usage is implied by 'Save a new persistent regression flow' and the note about scheduled and CI runs, but the description does not explicitly state when to use this versus update_flow or list_flows, nor does it mention prerequisites or exclusions.

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

All Regresco tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?