Skip to main content
Glama

Write the current version to a new .fmp12 file

patchwork_save
Destructive

Writes the current working version to a new .fmp12 file FileMaker can open, preserving the editable copy and versions so you can keep editing and save again.

Instructions

Write the current version to a new .fmp12 file that FileMaker can open. The working copy and its versions stay as they are, so you can go on editing and save again. Refused when the destination is the source file, or when it exists and force is not true.

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": {
      "dest": "<dest>"
    },
    "name": "patchwork_save"
  }
}

Input Schema

NameRequiredDescriptionDefault
destYesPath of the file to write. Must end in .fmp12 and differ from the source file.
forceNoReplace an existing file at dest. Inside the project folder only.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, so the bar is lower; the description still adds real value by stating that the working copy and its versions are left intact and by enumerating the two refusal conditions. It does not say what the call returns (path written, success payload), which is a minor remaining gap with no output schema.

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?

Three short sentences, front-loaded with what the tool does, then persistence behavior, then refusal conditions. No filler and nothing buried.

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 two-parameter write tool with annotations covering the safety profile, the definition covers purpose, persistence, and failure modes adequately. The only missing piece an agent might want is the return value and whether the write is atomic, neither of which is covered elsewhere.

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, but the description adds meaning beyond the schema by explaining the consequence of force being false (refusal when dest exists) and reinforcing that dest must differ from the source. It stops short of explaining the 'inside the project folder only' scope stated in the schema.

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?

States a specific verb and resource: writing the current version of the working copy to a new .fmp12 file that FileMaker can open. This is concrete and distinguishable from the mutation siblings (add_field, set_steps, etc.), though it does not explicitly contrast with the closest sibling, patchwork_push.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives clear context for use (the working copy and versions persist, so you can keep editing and save again) and explicit negative conditions: refused when dest equals the source file, or when dest exists without force. It stops short of naming any alternative tool, so it lands just under the top score.

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