Skip to main content
Glama
sql-mcp
by ohankay

commit_transaction

Commit all open transactions on a SQL Server connection to finalize pending changes and release transactional locks.

Instructions

COMMIT all open transactions on the connection.

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

Input Schema

NameRequiredDescriptionDefault
connectionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, idempotentHint=false, and destructiveHint=false, so the safety profile is covered. The description adds that the commit applies to ALL open transactions rather than one, which is meaningful multi-transaction scope not visible in annotations. It does not say whether an error is raised when nothing is open or what the call returns.

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?

One short, front-loaded sentence with the verb in capitals and no filler. It is perhaps too terse for the gaps it leaves, but nothing is wasted.

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 single-parameter commit tool with annotations covering safety and no output schema, this is close to adequate, but the unspecified 'connection' argument and the undefined no-open-transaction behavior leave real holes an agent would want filled.

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?

The single 'connection' parameter has 0% schema description coverage, and the description only alludes to it via 'on the connection'. It does not explain the accepted string format, that it is optional, or what a null default means (presumably the default connection) – the main remaining ambiguity an agent would face.

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?

The description states a specific verb and resource ('COMMIT all open transactions') and is clearly distinct from the rollback and begin siblings by name of operation. It stops short of explicitly contrasting with rollback_transaction, but the operation itself is unambiguous.

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

Usage Guidelines2/5

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

There is no guidance on when to commit versus when to use rollback_transaction or transaction_status, no mention of prerequisites (e.g., that a transaction must be open), and no indication of what happens when none are pending.

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