postgres-mcp-server

get_transaction_info

Retrieve details of an active PostgreSQL transaction including its name, server, database, and start time using its transaction ID.

Instructions

Get information about an active transaction, including its name, server, database, and when it started.

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": "get_transaction_info"
  }
}

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

A3.8/5.0

Behavior3/5

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

No annotations are provided, so the description carries the full burden. It correctly indicates the operation is a read ('Get information'), but does not disclose potential failure cases (e.g., invalid or completed transaction ID) or any safe behavioral traits beyond the basic purpose.

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, well-structured sentence that front-loads the action and resource, followed by specifics. Every word earns its place with no redundancy or fluff.

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 simple single-parameter tool with no output schema, the description adequately outlines the returned information. It is missing error-handling or edge-case context, but overall completeness is high given the low complexity.

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?

The schema already describes the 'transactionId' parameter as 'The transaction ID returned by begin_transaction' (100% coverage). The tool description adds no additional meaning or context beyond that, so it meets the baseline without enhancement.

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 tool's purpose with a specific verb ('Get information') and resource ('active transaction'), and lists the included fields (name, server, database, started). It effectively distinguishes from sibling tools like list_transactions (list) and transactional action tools.

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 when a transaction ID is available, but does not explicitly guide when to use this tool over alternatives like 'list_transactions' or other transaction-related tools. No exclusions or when-not-to-use guidance is provided.

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