Skip to main content
Glama

Delete an object from the working copy

patchwork_delete
Destructive

Deletes a script, layout, value list, custom function or field from a FileMaker file, refusing when other objects reference it so you can review them before forcing removal.

Instructions

Delete a script, layout, value list, custom function or field. Refused, with the list of what references it, when other objects reference it: show that list to the user, and only then retry with force=true. With force the references are left pointing at nothing and the result lists them for review. 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": {
      "kind": "<kind>",
      "name": "<name>"
    },
    "name": "patchwork_delete"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindYesKind of the object to delete.
nameYesExact name of the object. Table::Field for a field.
forceNoDelete even when other objects reference it. Only after the user has seen the list.
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.7/5.0
Behavior5/5

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

Annotations already declare destructiveHint=true, but the description adds substantial behavior beyond them: the refusal-with-reference-list guardrail, the exact consequences of force (references left pointing at nothing and reported back for review), and the fact that a new version is created. This tells the agent both the safe path and the cost of bypassing it.

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 tight sentences, front-loaded with what gets deleted, then the refusal/retry procedure, then recovery. No filler and no repetition of schema text.

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?

For a destructive mutation tool with no output schema, the description supplies the missing pieces: failure mode, recovery via force with its side effects, and reversibility via patchwork_undo. An agent has everything needed to call this safely without opening another tool's docs.

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 earns extra credit by explaining force semantically — it is not just 'delete anyway' but specifically leaves dangling references that get listed for review. The message/version-log parameter is only indirectly implied via 'makes a new version'.

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?

The first sentence states a specific verb (Delete) and enumerates the exact resource kinds (script, layout, value list, custom function, field), matching the enum in the schema. It is immediately distinguishable from sibling add_* tools and from patchwork_undo.

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?

It gives a clear conditional workflow: deletion is refused when references exist, the agent must surface the reference list to the user, and only then retry with force=true. It also points to patchwork_undo as the reversal path. It stops short of telling the agent to pre-check with patchwork_uses, so it is clear context rather than exhaustive when-to-use-vs-alternative guidance.

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