flowforge-mcp

flowforge_import_assistant

Creates a new assistant from an exported bundle and recreates its character, role, and flow to copy assistants across organizations or servers.

Instructions

Create a new assistant from an exported bundle (with its character, role and flow). Pair with flowforge_get_assistant include=['export'] to copy an assistant - including across orgs, using a different server (e.g. export from flowforge, import via flowforge-acme).

Returns: The created assistant (with its new ID).

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": {
      "params": "<params>"
    },
    "name": "flowforge_import_assistant"
  }
}

Input Schema

Name	Required	Description	Default
`params`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0Nov 6, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare that this is a non-readonly, non-idempotent, open-world, non-destructive creation operation. The description adds important context beyond annotations by noting that the result is a newly created assistant with a new ID and that imports can target a different server or org. It does not discuss duplicate handling, slug collisions, or required permissions, which are the main 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?

The description is short, front-loaded with the primary action, and then supplies the key copy workflow and return value. Every sentence carries useful information, with no filler.

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?

Given the rich input schema and the presence of an output schema, the description is largely complete: it explains the import source, cross-org/server workflow, and that a new assistant with a new ID is returned. It could be strengthened with notes on duplicate creation or conflict behavior, but the essential calling context is present.

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?

The input schema already documents the nested fields, including `data`, import toggles, and override options, so the description does not need to repeat them. It adds useful provenance for the `data` field by naming the exporting sibling and option, but does not explain override or toggle behavior beyond what the schema provides.

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 states a specific verb and resource: create a new assistant from an exported bundle, including character, role, and flow. It distinguishes itself from siblings by tying the input to `flowforge_get_assistant` with `include=['export']`, clearly separating it from ordinary assistant creation or retrieval.

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 explicit workflow guidance: pair with `flowforge_get_assistant` using `include=['export']` to copy an assistant, including across orgs and servers. It does not explicitly say when to prefer plain `flowforge_create_assistant`, but the import/copy scenario is clear enough for correct selection.

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

Deploy Server