Skip to main content
Glama

Open a FileMaker file as a working copy

patchwork_open
Destructive

Opens a closed .fmp12 file as a new versioned working copy (v000) and returns its version, account and object counts. Call it first, since every other tool edits this copy while the source stays untouched.

Instructions

Open a closed .fmp12 file as a new versioned working copy (v000) and return its summary: version, account and object counts. Call it first: every other tool works on this working copy. The source file is never modified, but it must be closed in FileMaker. Refused when a workspace already exists in the project folder, unless force=true, which deletes that workspace and all its versions. The password is read from the PATCHWORK_PASSWORD environment variable, never from an argument.

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": {
      "source": "<source>",
      "account": "<account>"
    },
    "name": "patchwork_open"
  }
}

Input Schema

NameRequiredDescriptionDefault
forceNoReplace an existing workspace: its versions are lost. Save first with patchwork_save. Inside the project folder only.
sourceYesPath of the .fmp12 file to open.
accountYesName of a Full Access account of the file.
projectNoFolder for the .patchwork workspace. Default: the server's project folder, else the source file's folder.
no_passwordNoTrue when the account has no password. Otherwise PATCHWORK_PASSWORD must be set.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.9/5.0
Behavior5/5

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

Annotations only say it is not read-only and is destructive; the description goes much further by naming the exact destruction ('deletes that workspace and all its versions'), the safety guarantee ('source file is never modified'), the open-file precondition, and the credential source. The force/warning detail is precisely the context annotations cannot convey.

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?

Four sentences in priority order: what it does and returns, the call-order rule, the safety/precondition, then the failure and override. No filler, and the most consequential constraint (destructive force) sits before the credential note.

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

Completeness5/5

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

Even without an output schema, the description enumerates the returned summary fields, and it covers preconditions, failure modes, credential handling and the destructive override. For a tool with 5 parameters that every later call depends on, nothing an agent needs to invoke it correctly is missing.

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 3 is the baseline, but the description adds real meaning: the password comes from PATCHWORK_PASSWORD and never from an argument (explaining why no password parameter exists and what no_password implies), and it restates force as an all-versions-deleting replacement tied to the project folder. Only the project parameter's defaulting behavior is left entirely to the schema.

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 ('Open a closed .fmp12 file as a new versioned working copy (v000)') plus the return payload (version, account and object counts). The 'Call it first' clause immediately separates it from the twenty sibling tools that operate on the copy.

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 ordering rule ('every other tool works on this working copy'), a precondition ('must be closed in FileMaker'), a refusal condition (existing workspace in the project folder) and the escape hatch (force=true). An agent knows both when to call it and when it will fail.

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