Skip to main content
Glama

move_flow_model

Relocates a flow model to a specified position relative to another block. Provide source and target UIDs and the target index.

Instructions

Move a flowPage block/model to a different position relative to another block.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sourceIdYesUID of the flow model to move
targetIdYesUID of the target flow model (reference position)
positionNoTarget sort position index

Implementation Reference

  • src/index.ts:265-281 (registration)
    Registration of the 'move_flow_model' tool with MCP server, including its input schema (sourceId, targetId, position) and handler that calls the /api/flowModels:move API endpoint.
    // 19. move_flow_model
    server.registerTool(
      "move_flow_model",
      {
        description: "Move a flowPage block/model to a different position relative to another block.",
        inputSchema: {
          sourceId: z.string().describe("UID of the flow model to move"),
          targetId: z.string().describe("UID of the target flow model (reference position)"),
          position: z.number().optional().describe("Target sort position index"),
        },
      },
      async ({ sourceId, targetId, position }) => {
        const qs = new URLSearchParams({ sourceId, targetId });
        if (position !== undefined) qs.set("position", String(position));
        return ok(await nocoFetch(`/api/flowModels:move?${qs}`, { method: "POST" }));
      }
    );
  • Handler function that constructs query params from sourceId, targetId, and optional position, then POSTs to /api/flowModels:move.
    async ({ sourceId, targetId, position }) => {
      const qs = new URLSearchParams({ sourceId, targetId });
      if (position !== undefined) qs.set("position", String(position));
      return ok(await nocoFetch(`/api/flowModels:move?${qs}`, { method: "POST" }));
  • Input schema definition for the move_flow_model tool with sourceId (required string), targetId (required string), and position (optional number).
    {
      description: "Move a flowPage block/model to a different position relative to another block.",
      inputSchema: {
        sourceId: z.string().describe("UID of the flow model to move"),
        targetId: z.string().describe("UID of the target flow model (reference position)"),
        position: z.number().optional().describe("Target sort position index"),
      },
  • Helper function nocoFetch that makes authenticated HTTP requests to the NocoBase API, used by the tool handler to call /api/flowModels:move.
    async function nocoFetch(path: string, options: RequestInit = {}): Promise<unknown> {
      const url = `${NOCOBASE_URL}${path}`;
      const res = await fetch(url, {
        ...options,
        headers: { ...reqHeaders, ...(options.headers as Record<string, string> | undefined) },
      });
      const text = await res.text();
      if (!res.ok) throw new Error(`HTTP ${res.status} ${res.statusText}: ${text}`);
      try { return JSON.parse(text); } catch { return text; }
    }
Behavior2/5

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

No annotations are provided, so the description must fully disclose behavior. It states 'move' but does not clarify whether the operation is destructive (removing from original position) or if it's a copy. It also omits side effects, permission requirements, or behavior on invalid references.

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 a single concise sentence that efficiently conveys the core action without unnecessary words. It is front-loaded with the verb and resource.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the complexity of flow models and the absence of an output schema or annotations, the description is quite brief. It does not explain return values, error behavior, or constraints like whether moving can affect child elements. Adequate for a simple operation but could be more complete.

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 has 100% description coverage for parameters (sourceId, targetId, position). The description adds minimal value beyond the schema, only clarifying the repositioning is 'relative to another block'. With full schema coverage, baseline score of 3 is appropriate.

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 clearly states the verb 'Move' and the resource 'flowPage block/model', specifying the operation 'to a different position relative to another block'. It effectively distinguishes from sibling tools like attach_flow_model and duplicate_flow_model.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives, such as when to use attach_flow_model or duplicate_flow_model instead. It lacks any context about prerequisites or conditions.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/puguhsudarma/nocobase-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server