Skip to main content
Glama
Flisk App Builder

Flisk App Builder

Official

stack_assign

Idempotent

Assign resources without a stack to a named stack by writing stack into each service.json; set move to true to reassign resources already in another stack.

Instructions

Assign resources that have no stack yet to a stack (writes stack into their service.json). A resource already in a stack is refused unless move is true, which moves it out of its current stack. Returns the structured envelope: data.stack and data.assigned (name and service.json path of each resource), or errors with a code and suggestions (for example the valid resource names). Set projectPath when the MCP server is not running from the project root.

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": {
      "stack": "<stack>",
      "resources": "<resources>"
    },
    "name": "stack_assign"
  }
}

Input Schema

NameRequiredDescriptionDefault
moveNoMove resources that are already in another stack instead of refusing them
stackYesStack name (kebab-case)
resourcesYesNames of the resources to assign
projectPathNoAbsolute path to the Flisk project root; run this operation from that directory.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.4.69
    • addedInput schema / properties / move
      Added value: +{
      +  "description": "Move resources that are already in another stack instead of refusing them",
      +  "type": "boolean"
      +}
  2. First observedv1.4.17

TDQS

A4.2/5.0
Behavior4/5

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

Goes well beyond the annotations by disclosing the guard behavior (refusal for already-assigned resources), the move semantics that override it, the exact return envelope (data.stack, data.assigned with name and service.json path), and the error shape with codes and suggestions. This is consistent with openWorldHint=false, idempotentHint=true and destructiveHint=false, since refusal-by-default is the non-destructive path.

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?

Front-loaded with the core operation and the refusal rule, then the return and error shapes, then the projectPath caveat. Every sentence carries information, though the error-suggestions sentence is slightly more detail than most agents need before calling.

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 four-parameter mutation tool with no output schema, the description covers preconditions, the override flag, the return envelope, error behavior, and the working-directory caveat. Nothing an agent needs in order 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.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so all four parameters are already documented, and this sets the baseline at 3. The description adds only marginal meaning: it clarifies that move removes a resource from its current stack and gives the condition under which projectPath is needed.

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 ('Assign resources ... to a stack') plus the concrete effect ('writes `stack` into their service.json'), which lets an agent understand the operation without opening the schema. It also distinguishes the no-stack case from the already-stacked case, so the scope is unambiguous.

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?

Gives clear preconditions: use it for resources with no stack, and already-stacked resources are refused unless move is true. It also notes projectPath should be set when the server is not running from the project root. No sibling alternative is named, but stack_list is the only related sibling and no true substitute exists for this mutation.

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