ALM X++ MCP Server

erp_call_session

Destructive

WHEN: to run several ERP tools in ONE ERP session, in order, when the steps depend on each other: open a form, click New, set field values, save, close. Each separate erp_call starts a new ERP session, so a form opened by one call is gone at the next; this tool keeps them together. The user's own F&O roles apply; a read-only instance refuses every step that could change data. ON EVERY INSTANCE, steps that can change data run only with confirm=true: without it nothing runs and you get the exact steps back, to show to the user. Set confirm=true only after the user agreed to those exact steps. All steps are checked BEFORE the first one runs, and the run stops at the first step that fails, so nothing is written after a failure. stepsJson: [{"tool":"form_open_menu_item","arguments":{...}}, ...], at most 15 steps. Close the forms you open.

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": {
      "instance": "<instance>",
      "stepsJson": "<stepsJson>"
    },
    "name": "erp_call_session"
  }
}

Input Schema

Name	Required	Description
`confirm`	No	Required true to run steps that can change data, on any instance, and only after the user agreed to those exact steps.
`instance`	Yes	Instance alias from erp_list_instances.
`stepsJson`	Yes	JSON array of steps: [{"tool":"<name from erp_list_tools>","arguments":{...}}].

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 29, 2026

changedInput schema / properties / confirm / description

Previous value: -"Required true to run steps that can change data on a protected instance."New value: +"Required true to run steps that can change data, on any instance, and only after the user agreed to those exact steps."

AddedOct 29, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Adds substantial context beyond annotations: F&O roles apply, read-only instances refuse data-changing steps, confirm=true is mandatory on every instance, all steps are validated before the first runs, execution stops at the first failure, and at most 15 steps are allowed. These disclosures align with destructiveHint and greatly reduce unsafe invocation risk.

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 dense but front-loaded with WHEN and structured around behavior, safety, and parameter shape. Every sentence contributes operational detail without redundant 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?

Covers the orchestration model, confirm gating, pre-validation, failure behavior, and step limit, which is enough to invoke safely. It stops short of describing the return payload after a confirmed run, though the absence of an output schema makes that a minor omission.

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 coverage is 100%, so the schema already documents each parameter. The description adds useful meaning beyond it, including the stepsJson array shape, the 15-step limit, and the sequencing semantics of confirm=true.

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?

States a specific verb and resource -- run several ERP tools in one ERP session, in order -- and explicitly contrasts with the sibling erp_call, which starts a new session per call. An agent can distinguish this tool from erp_call without opening either schema.

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

Usage Guidelines5/5

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

Opens with an explicit WHEN condition, gives the alternative (erp_call) and why it differs, and prescribes the confirm workflow and form-closing obligation. The conditions that select this tool versus a standalone call are clear.

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

All ALM X++ MCP Server tools Inspect

Try in Browser

Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.