Skip to main content
Glama
sql-mcp
by ohankay

rollback_transaction

Revert the currently open SQL transaction on a connection to undo uncommitted changes; safely does nothing if no transaction is active.

Instructions

ROLLBACK the open transaction on the connection (no-op when none is open).

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

Input Schema

NameRequiredDescriptionDefault
connectionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

B3.3/5.0
Behavior3/5

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

The description adds real context beyond annotations by disclosing the no-op behavior when no transaction is open. However, it does not state that pending changes are discarded, whether an error is raised, or what the call returns, and with destructiveHint=false the agent gets no signal about the consequence of uncommitted work being lost.

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 the parenthetical caveat placed where it is most useful. No wasted wording.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/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 definition covers the core action and the no-session edge case. It still leaves the connection default behavior and the fate of uncommitted work unexplained, which an agent needs before calling it.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% and the single connection parameter has a default of null, so the description carries the burden. Saying 'on the connection' only restates the parameter name; it never explains what a null/omitted connection resolves to (e.g., a default or currently active connection).

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 (ROLLBACK) and resource (the open transaction), so the operation is unambiguous. It does not explicitly name commit_transaction as the alternative, but the verb itself is distinctive enough to differentiate it from siblings.

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: rollback is the natural counterpart to commit, and 'no-op when none is open' hints at safe invocation. There is no explicit statement of when to prefer this over commit_transaction or when to check transaction_status first.

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