Skip to main content
Glama

Transaction Abort

transaction_abort
Destructive

Rolls back the most recent open transaction to restore a clean model state after failed or unwanted edits in FreeCAD.

Instructions

Roll back the most recent open transaction. Implementation note: FreeCAD 1.1 headless abortTransaction is unreliable, so the worker commits then undoes — net effect is a clean rollback.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "transaction_abort"
  }
}

Input Schema

NameRequiredDescriptionDefault
workspaceNoRun this call in this named workspace

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.5.7
    • addedInput schema / properties / workspace
      Added value: +{
      +  "default": "",
      +  "description": "Run this call in this named workspace",
      +  "title": "Workspace",
      +  "type": "string"
      +}
  2. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, but the description adds real context beyond them: the FreeCAD 1.1 abortTransaction unreliability and the commit-then-undo workaround, plus the reassurance that the net effect is a clean rollback. That mechanism disclosure is genuinely useful, though it omits failure behavior when no transaction is open.

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 short sentences with the action front-loaded and the implementation caveat second. The caveat earns its place because it changes how an agent should reason about side effects; nothing is redundant.

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 zero-required-parameter rollback with annotations covering the destructive profile and no output schema, the description covers purpose and mechanism adequately. Only edge-case behavior (no open transaction, error surface) is left unaddressed, which is minor.

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?

Only one optional parameter (workspace) and schema description coverage is 100%, so the schema already carries the meaning. The description never mentions workspace scoping, so it adds nothing over the structured field — baseline 3.

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?

States a specific verb and resource — 'Roll back the most recent open transaction' — which an agent can immediately distinguish from the commit sibling. It does not explicitly name transaction_commit or transaction_open, but the scoping ('most recent open') is precise enough to route correctly.

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

Usage Guidelines3/5

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

Usage is implied rather than stated: an agent can infer this is the discard path for an open transaction. There is no explicit prerequisite (an open transaction must exist), no statement of what happens when none exists, and no direct naming of the alternative transaction_commit.

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

Deploy Server

Other Tools