mcp-postgres

pg_switch_database

Switch the active database connection profile to change which database subsequent queries target. Select a profile from your saved configurations.

Instructions

Switch the active connection profile. All subsequent queries will use this profile unless overridden.

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": {
      "target": "<target>",
      "profile": "<profile>"
    },
    "name": "pg_switch_database"
  }
}

Input Schema

Name	Required	Description	Default
`target`	Yes	Target name from ~/.dbx/targets/
`profile`	Yes	Named profile to switch to

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2026.4.10-3Jul 25, 2026

TDQS

A3.5/5.0

Behavior2/5

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

Annotations are absent, so the description bears full responsibility. It states the tool modifies the active profile and affects subsequent queries, but does not disclose potential side effects (e.g., does it validate the profile, require an existing connection, or return a confirmation?)

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 extremely concise—a single sentence that front-loads the core action and adds only essential information about persistence to subsequent queries. No unnecessary words.

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?

Without an output schema, the description should clarify what the tool returns (e.g., success/error, confirmation) or that it operates as a side-effect. The current description is adequate for a state-changing tool but could be more complete by noting return behavior.

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 100%, with clear descriptions for both 'target' and 'profile'. The tool description adds minimal extra meaning beyond summarizing the action; it does not explain the relationship between the parameters or provide additional context.

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: 'Switch the active connection profile.' It uses a specific verb ('switch') and resource ('active connection profile'), and among the sibling tools, it uniquely identifies this function.

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 context ('All subsequent queries will use this profile unless overridden') but lacks explicit guidance on when to use it versus alternatives like pg_connect or pg_connection_status, and does not mention conditions where it should not be used.

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