Skip to main content
Glama
Sign In
Vibeflow

Vibeflow

by zorcec
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Verify task

verify_task

Run visual verification on a task: load its annotated page, compare the live element to the captured baseline, and append the outcome as a system comment.

Instructions

Run visual verification on a task with the Playwright engine: it loads the task's annotated page (url + selector) and compares the live element against the baseline captured at annotation time. MUTATES: every run appends a system comment with the outcome — pass dryRun to resolve the id and preview without launching a browser or writing anything. Pass url to check a different app URL for this run only, and timeoutMs (default 60000, refused VERIFY_TIMEOUT past it) for slow apps. A task with no baseline refuses with E_NO_BASELINE (re-annotate in vibeflow kanban to capture one); an unknown id with E_NOT_FOUND. Use it to check an annotated task before review; use update_task's setVerify to record the human verdict (this tool never sets it).

Input Schema

NameRequiredDescriptionDefault
idYesTask id — a full id, or any unique prefix of one, resolved by the same shared rule every other task tool uses. An id that matches nothing is refused with E_NOT_FOUND (this tool runs the CLI verify engine, which has its own code), and every refusal it returns carries a `suggestion`.
urlNoApp URL to verify against. Overrides the task's stored url for this run only; omit to use the task's own url.
dryRunNoPreview only: resolve the id and report that verification WOULD run, without launching a browser or writing anything.
timeoutMsNoPer-run timeout in milliseconds (1000-300000, default 60000). Exceeding it refuses with VERIFY_TIMEOUT — raise it for slow apps.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.22.0
    • addedInput schema / properties / dryRun / description
      Added value: +"Preview only: resolve the id and report that verification WOULD run, without launching a browser or writing anything."
    • addedInput schema / properties / timeoutMs / description
      Added value: +"Per-run timeout in milliseconds (1000-300000, default 60000). Exceeding it refuses with VERIFY_TIMEOUT — raise it for slow apps."
    • addedInput schema / properties / url / description
      Added value: +"App URL to verify against. Overrides the task's stored url for this run only; omit to use the task's own url."
  2. Changed1 schema field changedv0.21.1
    • addedInput schema / additionalProperties
      Added value: +false
  3. First observedv0.20.0

TDQS

A4.7/5.0
Behavior5/5

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

Annotations only declare readOnlyHint=false and non-idempotency; the description adds the actual side effect (every run appends a system comment), the dryRun escape hatch for a side-effect-free preview, timeout default and ceiling, and the specific refusal codes E_NO_BASELINE / E_NOT_FOUND / VERIFY_TIMEOUT. That is well beyond what the annotations convey and matches their non-read-only claim.

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?

Front-loaded with the operation, then a clearly flagged "MUTATES:" clause, then per-parameter notes and error codes — no wasted sentences. It is a dense single paragraph, so a reader must parse several compound clauses, but nothing is redundant.

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?

For a mutating tool with no output schema, it covers side effects, preview mode, error codes and parameter overrides. The only gap is the return payload shape of a successful run (what the appended comment/outcome looks like), which the agent must discover by calling it.

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?

Schema coverage is 100%, so the baseline is 3; the description still adds semantics by tying `url` to a run-only override, `timeoutMs` to the VERIFY_TIMEOUT refusal, and `dryRun` to the no-write guarantee. It largely mirrors the schema, hence 4 rather than 5.

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 concrete verb+resource: run visual verification on a task with Playwright, loading the annotated page (url + selector) and comparing the live element against the baseline. It also explicitly contrasts with update_task's setVerify ("this tool never sets it"), so an agent can distinguish it from the neighbouring task tools.

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?

Gives both when-to-use ("check an annotated task before review") and the alternative for the adjacent job ("use update_task's setVerify to record the human verdict"). It also names a preview path (dryRun) and the precondition failure (no baseline → re-annotate in `vibeflow kanban`).

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