Skip to main content
Glama

Put an existing field on a layout

patchwork_place_field

Place a field on a FileMaker layout by copying the look and label of an existing field, inserting it below or beside that field and shifting content to fit.

Instructions

Put a field on a layout. Copies the look and label of near, a field already on the layout, and inserts a row below it: objects underneath move down and the part grows. Refused when the field is already on the layout, or when side=right has no room. The version is dropped with an error if the field is not on the layout in the result. To create the field first, use patchwork_add_field. 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": {
      "layout": "<layout>",
      "field": "<field>",
      "near": "<near>"
    },
    "name": "patchwork_place_field"
  }
}

Input Schema

NameRequiredDescriptionDefault
nearYesA field already on the layout, as Occurrence::Field. The new field copies its look.
sideNobelow (default): a new row under `near`. right: beside `near`, if there is room.
fieldYesField to place, as Occurrence::Field, e.g. Clients::Status.
labelNoLabel text. Default: the field name.
layoutYesExact name of the layout. Names come from patchwork_list kind=layouts.
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.9/5.0
Behavior5/5

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

Beyond the annotations (readOnly=false, idempotent=false, destructive=false), the description discloses the concrete effect: it copies the look and label of `near`, inserts a row below, shifts objects down and grows the part. It also covers failure modes (refusal conditions, version dropped with an error) and versioning (makes a new version; patchwork_undo reverses 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?

Front-loaded with the action, then effect, then failure conditions, then alternatives and versioning. Every sentence carries information an agent needs; no filler or restated title.

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 non-readonly, non-idempotent mutation with 7 parameters and no output schema, the description covers effects, refusal conditions, error behavior, version/undo semantics, and the add-first alternative. Nothing an agent needs to call 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 the baseline would be 3, but the description adds meaning beyond the schema — it explains that `near` supplies the copied look and label, that `side=right` fails when there is no room, and the row-insertion consequence of the placement. That is real semantic value, though the side/label defaults largely restate schema text.

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 description opens with a specific verb and resource ("Put a field on a layout") and immediately contrasts with the sibling that creates fields (patchwork_add_field). An agent can distinguish this from add_field without opening either 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?

It explicitly routes the agent: "To create the field first, use patchwork_add_field," and states the preconditions under which the call is refused (field already on layout, side=right with no room). Both the when-to-use and the when-not conditions are spelled out.

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