Skip to main content
Glama

Change the colors, fonts or name of a theme

patchwork_retheme

Rewrite a FileMaker theme by replacing colors, swapping fonts, or changing its display name. Creates a new reversible version so you can restyle layouts without touching the source file.

Instructions

Rewrite one theme: replace colors, replace fonts, or change its display name. Read the current colors with patchwork_palette first. For colors and fonts set on layout objects rather than in the theme, use patchwork_recolor_layouts. Makes a new version; patchwork_undo reverses it.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "patchwork_retheme"
  }
}

Input Schema

NameRequiredDescriptionDefault
fontsNoOld font to new font, each as "WinName,MacName": {"Arial,Helvetica": "Inter,Inter"}.
themeNoDisplay or internal name of the theme. Default: the theme most layouts use.
colorsNoOld color to new color, as 6-digit hex without #: {"0091CE": "2F5D50"}.
renameNoNew display name of the theme.
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.4/5.0
Behavior4/5

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

Annotations already declare the safety profile (readOnly false, destructive false, idempotent false), so the description's job is additive, and it delivers: it discloses that a new version is created and that patchwork_undo reverses it. It does not mention the dry_run escape hatch or any permission requirements, which are the remaining behavioral gaps.

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 the core operation, then the prerequisite, then the sibling routing rule, then the reversibility note. No filler or redundancy.

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 mutation tool with six params, no output schema, and nested objects, the description covers purpose, prerequisites, sibling disambiguation, and version/undo behavior. The only omission is dry_run, which the schema fully documents, so completeness is strong but not exhaustive.

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%, with each of the six parameters documented in-schema including the hex-without-# format, the WinName,MacName font key format, and dry_run semantics. The description adds no parameter meaning beyond the schema, so the baseline of 3 applies.

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 plus the three exact operations: 'Rewrite one theme: replace colors, replace fonts, or change its display name.' An agent can immediately distinguish this theme-level edit from patchwork_recolor_layouts, which the description also names.

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 prerequisite ('Read the current colors with patchwork_palette first'), an explicit routing rule to the sibling for layout-object-level changes, and names the reversal path. When-to-use and when-to-use-something-else are both covered.

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