Skip to main content
Glama
Flisk App Builder

Flisk App Builder

Official

config_regenerate

DestructiveIdempotent

Regenerate master config files from project.json, previewing changes by default; set dryRun false to write and discard manual edits.

Instructions

Regenerate the master config files in .flisk/.flisk-out/ from .flisk/project.json. A dry run by default, which returns the planned changes as data.changes (each file's status and lineDiff) with data.hasChanges; set dryRun to false to write them and get the same list, which discards hand edits in those generated files. Set projectPath when the MCP server is not running from the project root.

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": "config_regenerate"
  }
}

Input Schema

NameRequiredDescriptionDefault
dryRunNoDefault true: show what would change. false rewrites the files and discards hand edits in them
projectPathNoAbsolute path to the Flisk project root; run this operation from that directory.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.4.17

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the annotations, it discloses the non-writing default, the planned-change result fields, the same result list in write mode, and the fact that writing discards hand edits in generated files. These details make the safety profile and consequences concrete, and the optional write behavior is consistent with readOnlyHint=false and destructiveHint=true.

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?

The description is front-loaded and compact, with all three sentences contributing actionable information. Its middle sentence densely combines output structure, mode switching, and the destructive caveat, which slightly reduces scanability.

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 two-parameter tool with no output schema, it supplies the source and target locations, default behavior, result shape, write-side effects, and project-path condition. This is sufficient for an agent to invoke both preview and write modes correctly and safely.

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 already 100%, but the description adds useful context by connecting dryRun to preview-versus-write behavior and explaining the conditional need for projectPath. It also clarifies what each mode returns, although some of the parameter wording repeats 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?

The description uses a specific verb and identifies both the source, .flisk/project.json, and the generated targets in .flisk/.flisk-out/. This concrete scope makes regeneration unambiguous and distinguishes it from other configuration-related operations without relying on sibling names.

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 clear operational guidance: use the default dry run to preview changes, set dryRun to false to write them, and set projectPath when the server is not running from the project root. It does not explain the broader workflow conditions that should trigger regeneration or when another configuration tool would be preferable.

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