Skip to main content
Glama

Validate flow

validate_flow

Check a flow file's structure, including step kinds and their keys, without running the flow. Use it to catch structural errors before execution.

Instructions

Check a flow file's structure (step kinds and their keys) without running it.

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": {
      "path": "<path>"
    },
    "name": "validate_flow"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/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 behavioral burden. It usefully discloses the key non-execution behavior and that validation is structural, but it does not state whether the file is modified, how validation errors are reported, or what file-access requirements exist.

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 efficient sentence with no wasted words. The core action and the non-execution constraint are both front-loaded.

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

Completeness3/5

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

For a simple validation tool, the description covers the essential action and non-execution behavior. However, with no annotations and no output schema, it should say more about what a validation result contains or how structural errors are surfaced.

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 0%, so the description must compensate for the single 'path' parameter. Saying 'a flow file's structure' implies the path points to a flow file, adding some meaning beyond the schema title 'Path,' but format, relative-vs-absolute handling, and existence requirements are unstated.

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?

The description states a specific verb and resource: 'Check a flow file's structure.' The parenthetical clarifies what structure means (step kinds and their keys), and 'without running it' scopes the tool away from execution. It does not reference siblings, but the sibling names are unrelated enough that this is not a major gap.

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?

'Without running it' implicitly contrasts this with executing a flow, which gives some usage context. However, there is no explicit when-to-use guidance, no prerequisites, and no named alternative for full execution or report generation.

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