Skip to main content
Glama
Sign In
Postgres MCP Pro

Postgres MCP Pro

by sparta2025
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

get_database_locks

Identify current database locks and blocking queries to pinpoint and resolve contention issues.

Instructions

Show current database locks and blocking queries.

Args:
    database_url: Database URL (optional, uses DATABASE_URL from .env if omitted).

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

Input Schema

NameRequiredDescriptionDefault
database_urlNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.2

TDQS

A3.5/5.0
Behavior2/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. 'Show' implies a read-only operation, but the description does not explicitly disclose safety, required permissions, potential performance impact, or what happens on failure. It adds no behavioral context beyond the core function.

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 compact and front-loaded: the core purpose appears in the first sentence, followed by a concise Args section. Every part earns its place, and the formatting is easy for an agent to parse.

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 tool with one optional parameter and no output schema, the description covers the essentials: what it shows and how to pass an optional URL. However, it omits usage context, return shape, and any behavioral caveats, leaving a noticeable gap for an agent deciding whether this is the right tool.

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

Parameters4/5

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

The schema has zero description coverage, so the description must carry parameter meaning. It does: database_url is explained as optional and falls back to DATABASE_URL from .env. This adds meaningful context beyond the raw schema, though URL format or connection behavior is not detailed.

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 states a specific action ('Show') on a specific resource ('current database locks and blocking queries'), making the tool's purpose immediately clear. It also distinguishes it from sibling tools like get_active_queries by focusing on locks and blocking, not just running queries.

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?

No guidance is given about when to use this tool instead of alternatives such as get_active_queries or analyze_db_health. There are no exclusions, prerequisites, or context cues beyond the basic function.

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

Deploy Server

Other Tools