Skip to main content
Glama
Yan-Vi

easy-spec-mcp

by Yan-Vi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

create_flow

Create a new empty flow for Easy Spec Playwright projects. Define the flow name, notes, folder, and preconditions to set up a structured automation scenario.

Instructions

Create a new, empty flow.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNo
nameYes
notesNoCaveats or instructions for anyone editing this flow.
folderNo
projectNoPath to the project root (same folder the side panel connects to). Defaults to the EASYSPEC_PROJECT environment variable if omitted.
descriptionNo
preconditionsNoSetup/state assumed to already hold before this flow runs.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.4

TDQS

A3.5/5.0
Behavior3/5

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

The description implies creation of a flow but does not mention side effects, error conditions, or required permissions. No annotations are provided to supplement this.

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 a single, concise sentence that gets straight to the point without superfluous details.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool is simple, but the lack of parameter explanations and any success/failure behavior leaves gaps for an agent trying to invoke it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 43%, and the description does not explain the purpose of key parameters like id, name, folder, or description.

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 clearly states the action (create) and the resource (flow), and is distinct from sibling tools like list_flows and delete_flow.

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?

There is no explicit guidance on when to use this tool versus alternatives, but the intent is obvious given the tool name and description.

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