Skip to main content
Glama

adb_workflow_validate

Validate workflow JSON definitions without executing them to catch structural errors and preview the execution plan.

Instructions

Validate a workflow JSON definition without executing it. Reports structural errors and shows the execution plan.

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": {
      "workflow": "<workflow>"
    },
    "name": "adb_workflow_validate"
  }
}

Input Schema

NameRequiredDescriptionDefault
workflowYesWorkflow JSON string to validate

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.1.6
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  2. Changed1 schema field changedv1.1.3
    • removedInput schema / additionalProperties
      Removed value: -false
  3. First observedv1.1.1

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It does disclose the key behavioral fact that nothing is executed and that output includes structural errors plus an execution plan, which is valuable since there is no output schema. It omits error semantics (e.g., how invalid JSON is reported), size limits, and whether validation touches any device state.

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 short sentences, zero redundancy, and the non-execution qualifier is front-loaded where an agent will read it first.

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 one-parameter, non-destructive validation tool this covers purpose, the critical non-execution guarantee, and the general shape of the return value. The remaining gap is minor: it does not say how to interpret or act on reported errors, or that a validated definition can be passed to adb_workflow_run.

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 100% and the single 'workflow' parameter is documented as a 'Workflow JSON string to validate'. The description adds no format details, required fields, or example shape beyond what the schema already states, so baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Specific verb plus resource: 'Validate a workflow JSON definition' with the scope limiter 'without executing it'. This implicitly separates it from the sibling adb_workflow_run, but it never names that sibling or adb_workflow_list explicitly.

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 phrase 'without executing it' implies this is the dry-run/pre-flight step before adb_workflow_run, but that guidance is only implied. There is no explicit 'use this when...' or 'do not use this to actually run a workflow' routing statement.

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