Skip to main content
Glama

Add a custom value list to the file

patchwork_add_value_list

Create a custom value list in a FileMaker file with verified, versioned and reversible edits, so added values re-read correctly or the version is rolled back with an error.

Instructions

Create a custom value list from a fixed list of values. The stored values are re-read, and the version is dropped with an error if FileMaker kept different ones. To change an existing value list, read it with patchwork_show and send it back with patchwork_replace. 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": {
      "name": "<name>",
      "values": "<values>"
    },
    "name": "patchwork_add_value_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesName of the new value list.
valuesYesThe values, in display order: ["Bronze", "Silver", "Gold"].
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.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, idempotentHint=false, destructiveHint=false, so the safety profile is covered. The description adds real behavior beyond that: stored values are re-read and the version is dropped with an error if FileMaker kept different ones, a new version is created, and undo reverses it. It stops short of describing the returned payload or the dry_run path, which the schema covers instead.

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?

Four short sentences, front-loaded with the core action and followed by verification behavior, the modify alternative, and the undo path. Every sentence carries information, though the clause 'the version is dropped with an error if FileMaker kept different ones' is slightly dense and takes a second read.

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 four-parameter write tool with no output schema, the description supplies what annotations cannot: version creation, undo, read-back verification, and the correct alternative for edits. The dry_run and message parameters are only documented in the schema, but that coverage is complete, so nothing critical is missing.

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%, including a concrete example for the values array ('["Bronze", "Silver", "Gold"]') and an explicit statement of dry_run semantics, so the schema does the heavy lifting. The description adds no parameter-level detail beyond noting that a version is made, which is the expected baseline when the schema is fully documented.

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?

Opens with a specific verb and resource: 'Create a custom value list from a fixed list of values.' It further distinguishes itself from siblings by naming patchwork_replace as the tool for changing an existing list and patchwork_show as the read path, so an agent can separate add-vs-modify without opening a 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 alternative path for the adjacent case: to modify an existing value list, read it with patchwork_show and send it back with patchwork_replace. It also states the reversal path (patchwork_undo), so both the 'when' and the 'instead' are covered rather than implied.

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