flowforge-mcp

flowforge_end_call

DestructiveIdempotent

Terminates an in-progress call by call ID, or ends all active calls at once with all_calls=true; it immediately hangs up and cannot be undone.

Instructions

End an in-progress call, or end every active call at once.

Provide call_id to end one call, or set all_calls=true to terminate all running calls. This immediately hangs up; it cannot be undone.

Args: params: call_id (optional) and all_calls (default false).

Returns: A confirmation message or the API result.

Error Handling: Returns "Error: ..." if neither call_id nor all_calls is provided, 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_end_call"
  }
}

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

Behavior4/5

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

Beyond the annotations, the description adds that the operation immediately hangs up and cannot be undone, and it documents the error condition when neither parameter is supplied. The annotations already mark this as destructive, read-write, and idempotent, so this is useful additional behavioral context.

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 main action and then organized into Args, Returns, and Error Handling. It is slightly verbose and the Returns section is less necessary because an output schema exists, but the structure is clear.

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 simple one-parameter destructive tool, the description covers purpose, parameter selection, irreversibility, return behavior, and error handling. Combined with the annotations and output schema, an agent has enough information to call it correctly.

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?

With schema description coverage reported as 0%, the description compensates by explaining that call_id is optional, all_calls defaults to false, and one or the other must be supplied. It does not repeat the schema detail that all_calls ignores call_id, but it still adds meaningful parameter guidance.

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: end an in-progress call or every active call at once. It clearly distinguishes single-call termination from bulk termination, which is the key behavioral split for this tool.

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 explicitly says to provide call_id to end one call or set all_calls=true to terminate all running calls, and it notes that supplying neither produces an error. It does not name alternative tools, but the usage conditions are otherwise clear.

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

Deploy Server