flowforge-mcp

flowforge_assign_phone_number

Idempotent

Assign an AI assistant to a phone number so it answers inbound calls, or unassign the current assistant to detach it.

Instructions

Assign an assistant to a phone number (so it answers inbound calls), or unassign the current one.

Provide agent_id to assign, or set unassign=true to detach.

Args: params: phone_number_id, plus either agent_id or unassign.

Returns: The API result, or a confirmation message.

Error Handling: Returns "Error: ..." if neither agent_id nor unassign is supplied, or on an API failure.

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

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/5.0

Behavior4/5

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

Annotations already declare the operation is not read-only, is idempotent, is non-destructive, and touches an open world. The description adds useful behavior beyond that: it explains that assignment controls inbound call answering, describes unassignment, and documents the error when neither agent_id nor unassign is provided.

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 with the core action and then structured into Args, Returns, and Error Handling sections. It is somewhat repetitive around the either/or rule, but no sentence is seriously wasteful.

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?

For a mutation tool with nested parameters and an output schema, the description covers the main action, parameter usage, return behavior, and error handling. It could be slightly more complete by stating prerequisites such as needing an owned phone number and a valid agent, but the schema covers some of that.

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 description coverage is reported as 0%, so the description must compensate. It names phone_number_id and explains the either/or relationship between agent_id and unassign, including that an error results if neither is supplied.

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 states a specific operation: assign an assistant to a phone number so it answers inbound calls, or unassign the current assistant. That is clear verb plus resource, but it does not explicitly distinguish this tool from the sibling flowforge_manage_phone_number.

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: provide agent_id to assign, or set unassign=true to detach. It also states that an error is returned if neither is supplied, which is a useful exclusion. It does not name sibling alternatives such as flowforge_manage_phone_number.

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

Deploy Server