Skip to main content
Glama

Transaction Commit

transaction_commit

Commits the most recent open transaction in AnkusDrive, preserving all changes made during it.

Instructions

Commit the most recent open transaction; changes are kept.

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

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.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false and destructiveHint=false, so the safety profile is known. The description adds the one behavioral fact annotations cannot convey, that changes are kept rather than discarded, which is exactly the contrast with abort. It omits error behavior, whether nested or stacked transactions are affected, and whether the commit is scoped to the named workspace.

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?

One short sentence, front-loaded with the verb, with no filler. The outcome clause carries real information rather than restating the name.

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 single-parameter, annotation-covered, no-output-schema tool, the description conveys purpose and the persistence consequence. The only meaningful gaps are the precondition (open transaction required) and error/edge behavior, which are minor for this complexity level.

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 with 100% schema description coverage, so the schema already documents 'workspace' fully. The description adds nothing about workspace semantics (e.g. whether a commit can target a different workspace than the open transaction), making this the baseline case.

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?

A specific verb and resource ('Commit the most recent open transaction') plus the outcome ('changes are kept') makes the operation unmistakable and naturally contrasts with the sibling transaction_abort. It stops short of explicitly naming the sibling alternatives, so it's clear but not maximally differentiated.

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 only implied: you commit after opening a transaction when you want to persist work. There is no statement of the precondition (a transaction must be open), no mention of transaction_abort as the alternative path, and no guidance on what happens on commit failure or with no open transaction.

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