Skip to main content
Glama
sql-mcp
by ohankay

transaction_status

Read-onlyIdempotent

Shows @@TRANCOUNT, XACT_STATE(), and isolation level for a connection so users can inspect active or failed transaction state.

Instructions

Show @@TRANCOUNT, XACT_STATE() and isolation level of 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": "transaction_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
connectionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered by structured data. The description contributes the concrete payload (transaction count, XACT_STATE, isolation level), which is useful behavior beyond the annotations. It says nothing about what happens when no transaction is active or how the target connection is resolved, leaving a gap for a diagnostic tool.

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 front-loaded sentence with no filler; every token (the three state expressions) is substantive. It is as short as it can be while naming the returned values. Slightly terse rather than structured, but nothing is wasted.

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?

This is a low-complexity, zero-required-parameter read tool with no output schema, and the description enumerates the returned fields, which is the main thing an agent needs. The only real omission is default-connection semantics. Given the simplicity of the tool, that is a minor gap rather than a blocking one.

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 0% for the single optional 'connection' parameter, so the description has to carry the meaning. The phrase 'of the connection' implies the parameter selects which connection's state is reported, which is some help. However, it never explains what a null/default value resolves to (current session? most recent connection?), so the key ambiguity remains.

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 ('Show') and enumerates exactly what is reported: @@TRANCOUNT, XACT_STATE() and isolation level. That is far more precise than the name alone and lets an agent recognize it as a transaction-state inspection tool rather than a mutator like begin/commit/rollback. It stops short of explicitly contrasting itself with those siblings, so a 4 rather than a 5.

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: an agent can infer it should call this to inspect transaction depth/state before deciding to commit or roll back. There is no explicit when-to-use, no stated prerequisites (e.g. must already be in a transaction), and no named alternative such as execute_sql for ad-hoc queries. Adequate but with clear gaps.

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