Skip to main content
Glama

adb_test_gen_save

Save generated workflow JSON to the workflows directory so it can be executed later with adb_workflow_run.

Instructions

Save a generated workflow JSON to the workflows directory for later execution with adb_workflow_run.

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

Input Schema

NameRequiredDescriptionDefault
nameYesWorkflow name (used as filename)
workflowYesWorkflow JSON string to save

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

B3.3/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden for a filesystem write. It discloses the destination directory but says nothing about overwrite-vs-error behavior when 'name' already exists, whether the directory is created if absent, path sanitization of the filename, or what the tool returns on success/failure. For a mutation tool with zero annotation coverage, these are significant omissions.

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?

A single front-loaded sentence with the action, the artifact, the destination, and the follow-up tool. No wasted wording and nothing buried.

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 two-parameter persistence tool with no output schema, the description covers the essentials of what and why. The remaining gap is mutation semantics (overwrite, validation of the JSON string, error surface), which matters more here because no annotations exist to fill it.

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 both parameters are documented in the schema, including that 'name' is used as the filename. The description adds nothing beyond that baseline, so a 3 is appropriate.

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 uses a specific verb ('Save') with a specific resource ('generated workflow JSON') and destination ('workflows directory'), which lets an agent distinguish it from adb_workflow_run (execution) and adb_workflow_validate. It does not name the generator siblings (adb_test_gen_from_ui, adb_test_gen_from_intents) as its upstream, but the purpose is unambiguous.

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 'for later execution with adb_workflow_run' implies the save-then-run sequencing and points at the correct downstream tool. However, it never states when to choose this versus re-generating, or any prerequisites such as that a workflow must first be produced by a gen tool.

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