Skip to main content
Glama

Add steps at the end of a script

patchwork_append_steps

Append new steps to the end of an existing FileMaker script while keeping its current steps intact. Use it instead of set_steps when no existing step changes; creates a new reversible version.

Instructions

Add steps at the end of an existing script and keep the steps it has. Use it instead of patchwork_set_steps when no existing step changes. The whole script is re-read, and the version is dropped with an error if a step came back different. To create the script, use patchwork_add_script. Makes a new version; patchwork_undo reverses 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": {
      "script": "<script>",
      "steps": "<steps>"
    },
    "name": "patchwork_append_steps"
  }
}

Input Schema

NameRequiredDescriptionDefault
stepsYesOne step per line, as FileMaker shows them: Set Variable [ $n ; Value: 1 ], If [ $n > 0 ], Show Custom Dialog [ "Title" ; "Message" ; Buttons: "OK", "Cancel" ], End If, # comment. Or <Step> XML.
scriptYesExact name of the script that gets the steps.
dry_runNoOnly write the patch file to .patchwork/ and return its path. Nothing is applied, no version is made.
messageNoWhat this change does, kept in the version log. Default: a short description of the change.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.5/5.0
Behavior5/5

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

Beyond the annotations, it discloses that the entire script is re-read, that the write is aborted with an error if any existing step differs, that a new version is created, and that patchwork_undo reverses it. That is failure-mode, concurrency and reversibility context the annotations do not carry.

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?

Five short sentences, front-loaded with the core action and the sibling routing, with no filler. Slightly dense with clauses, but every statement carries information.

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 non-idempotent write tool with no output schema, it covers scope, failure behavior, versioning and reversibility. It does not say what a successful call returns (e.g. the new version identifier or step count), a minor remaining gap.

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 100%, so steps, script, dry_run and message are already documented in the schema. The description adds no syntax or format detail beyond it, which is the expected baseline when the schema does the work.

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 specific verb and resource ('Add steps at the end of an existing script') plus the defining behavior ('keep the steps it has'), which separates it from patchwork_set_steps and patchwork_add_script without needing the schema.

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 an explicit selection rule: use this instead of patchwork_set_steps when no existing step changes, and use patchwork_add_script to create the script. Both the alternative and the condition that selects it are named.

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