postgres-mcp-server

rollback_transaction

Undo all changes made in an active database transaction by specifying its transaction ID.

Instructions

Rollback an active transaction, undoing all changes made within it.

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": {
      "transactionId": "<transactionId>"
    },
    "name": "rollback_transaction"
  }
}

Input Schema

Name	Required	Description	Default
`transactionId`	Yes	The transaction ID returned by begin_transaction

Schema Changelog

Changes observed during successful MCP inspections.

First observedv3.0.3May 30, 2026

TDQS

A4.1/5.0

Behavior4/5

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

With no annotations provided, the description bears full burden. It discloses the core behavioral trait of undoing all changes, which is sufficient for a simple rollback. Could mention that the transaction is closed afterward, but overall transparent.

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 a single, front-loaded sentence that concisely conveys the purpose and effect. Every word is earned; no fluff.

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?

Given low complexity (one simple parameter, no output schema, no nested objects), the description adequately covers what the tool does and the parameter meaning. Sibling tools provide context for differentiation.

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?

Schema description coverage is 100% for the sole parameter 'transactionId', with a clear schema description. The tool description adds no further meaning, meeting the baseline of 3.

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 clearly states the verb 'rollback', the resource 'active transaction', and the effect 'undoing all changes'. It distinguishes from sibling tools like 'commit_transaction' and 'begin_transaction'.

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?

The description implies usage for undoing changes within a transaction, but provides no explicit guidance on when to use this versus alternatives like 'commit_transaction' or 'rollback_transaction' itself. No when-not-to-use or context is given.

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