flowforge-mcp

flowforge_update_organization

Idempotent

Update organization settings and concurrency caps, or read and set the test phone number used by test calls; read current values first when changing concurrency.

Instructions

Change organization settings and concurrency caps, or read/set the org test phone number (the number test calls ring). Read current values first with flowforge_get_organization include_concurrency=true.

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_update_organization"
  }
}

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

A3.6/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=false, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is largely covered. The description adds a useful nuance that some actions are pure reads despite the non-read-only hint, but says nothing about whether updates are partial merges, what happens to unspecified settings, or permission requirements.

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?

Two sentences, front-loaded with the mutation capability and then the read/set variant, followed by the safe-read prerequisite. No filler, though the parenthetical explanation of the test number is slightly redundant for an experienced caller.

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?

With annotations covering the safety profile and an output schema present, the description does not need to explain return values. What an agent needs to choose an action and pre-read state is present; only partial-update semantics remain undocumented.

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 reported as 0% at the top level, so the description must compensate; it partially does by enumerating the four capabilities so an agent can pick an action. However it adds no detail on the fields payload beyond what the nested schema already spells out in its field lists.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names specific actions on a specific resource: changing org settings and concurrency caps, and reading/setting the org test phone number, with a parenthetical clarifying what that number is. This maps onto the four action enum values, though 'settings' stays slightly generic until the schema's field lists are read.

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 concrete pre-call guidance ('Read current values first with flowforge_get_organization include_concurrency=true'), naming the sibling tool and even the flag to pass. It does not state when not to use this tool or which flowforge_manage_phone_number operations overlap with the test-phone-number actions.

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

Deploy Server